Open
1 of 1 issue completedDescription
Summary
Track progress on introducing sub-types for our R-, I-, B-, S-, U-type instruction formats to improve clarity, tooling and testing.
Motivation
- Mixed encodings in each format (e.g. immediates vs. hard-coded bits)
- Ambiguous docs some instructions don't match any type
- Coarse tests that can’t target specific bit-patterns
Proposal
- Add a
subtype
field to our instruction schema. - Example sub-types:
R.aqrl
— acquire release Rtype
- Annotate existing instructions.
- Create test suite to validate schema in UDB
Next Steps
- Create full list in a readable format to ask for reviews