chipsalliance / chipsalliance/rocket-chip

SLOI, SROI also need *_RV32 version; how REV, REV8, ORC_B instructions are related to b-ext.

Open
#2,549 1 comment 0 reactions 0 assignees View on GitHub
proposal
Dominant language
Scala
Stars
3.9k
Forks
1.3k
Avg merge
5d 13m
Merged PRs (30d)
1

Description

1. Like RORI has RORI_RV32 version, I think SLOI and SROI also need *_RV32 version.
https://github.com/chipsalliance/rocket-chip/blob/f1521796c292ee87958df6ea52f12145d869c83f/src/main/scala/rocket/Instructions.scala#L823

2. REV, REV8, ORC_B are instructions from Zbb, while bitmanip defines them as pseudo instructions. Is it hte case? where is the REV, REV8 and ORC_B spec definitions?

Contributor guide

Open the contributing guide

Research direction

Start with the referenced Instructions.scala entry around line 823 and compare the existing RORI_RV32 definition with SLOI and SROI. Then verify the RISC-V bitmanip specification for REV, REV8, and ORC_B and determine whether Rocket Chip treats them as Zbb instructions or pseudo-instructions. Done means the RV32 variants and instruction relationships are correctly represented and verified against the specification.

Written by the indexing model from the issue text.

Assessment

Tech stack
scala
Domain
embedded-iot
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.