Be explicit about required sext/zext
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 10
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Scalars smaller than xlen are extended according to their type up to 32-bits, then sign-extended to xlen. rvcc.py should indicate when this takes place.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading rvcc.py and locating the handling of scalars smaller than xlen. Trace where type-based extension and sign extension are modeled, then make the output explicitly indicate when sext or zext occurs. Done means the relevant scalar-extension behavior is visible in rvcc.py's results; no test file is named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100