Support RISCV64 vector extension. #6
Merged
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
hasenbanck
force-pushed
the
vector_aes
branch
7 times, most recently
from
ad3ae33 to
aefe360
Compare
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 old scalar crypto RISC-V backend and adds a vector crypto based backend instead. Both extensions have no real world implementations, but since application class CPUs will have the vector extension implemented, I have a feeling that vector crypto support will be dominating (since it's efficienter). There is currently no runtime detection support available.
The implementation is written with inline ASM and is supported by the latest stable version (1.80).
I moved the support behind a experimental feature. Implementd #2