[rtl] XLEN cleanup #417
Merged
[rtl] XLEN cleanup #417
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
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 removes the
data_width_cpackage constant, which defines the "native data width" of the whole NEORV32 processor.This is very a first step towards supporting the RISC-V 64-bit ISA
rv64.The SoC (so all memories and peripherals) will be 32-bit only. The CPU core itself will provide a new configuration generic
XLENthat allows to specify the core's native data width (32-bit or 64-bit). This generic is not yet available!This is still very early stuff and highly experimental! Full RV64 support will/might be added somewhere in the future.