PLIC Priority RegFieldDesc fix off-by-one #2718
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related issue: None
Type of change: other enhancement
Impact: API modification
Development Phase: implementation
Release Notes
PLIC Priority registers are now explicitly named with a suffix. This prevents tooling which assumes that the "first" register in a group should have the 0th index ending up with Priority[2] ending up in a register called priority_1, and so on.