✨ [CFU] add support for custom R5-type instructions #452
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
stnolting
added
enhancement
add R5-type instruction example
add R5-type instructions
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR adds (optional) support of R5-type instructions to the Custom Functions Unit (CFU). Users can now implement custom instructions with up to 4 source operands.
👍 Idea triggered by @jimmy9799 in discussion #446.
ℹ️ Since the RISC-V ISA spec. does not define R5-type instruction formats (yet), a NEORV32-specifc format is defined that is based on the official RISC-V R4-type format.
ℹ️ The
custom-2andcustom-3OPCODEs are used to define the CFU R5-type instructions.