| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
- After questions from the architecture review and subsequent cryptography
task group meetings, we have stopped overlapping the aes32* and aes64*
instruction encodings.
- We've done this in the name of removing complexity, because opcode space is
not as tight as we thought it was when we originally overlapped them.
- Change affected by updating the aes32* opcodes only.
On branch master
Your branch is up-to-date with 'origin/master'.
Changes to be committed:
modified: opcodes-rv32k
modified: parse_opcodes
|
|
- Change AES32* and SM4* instructions back to regular R-type encoding.
On branch scalar-crypto-v0.9.2
Changes to be committed:
modified: opcodes-rv32k
modified: opcodes-rv64k
modified: opcodes-rvk
modified: parse_opcodes
|
|
Co-authored-by: Megan Wachs <megan@sifive.com>
|
|
- Adds opcodes for RV32 and RV64 scalar crypto.
- opcodes-rvk contains encodings which are for RV32 and RV64 base ISAs
- opcodes-rv32/64k contains encodings which are for RV32 or RV64
- parse_opcodes has been modified:
- Wnable instructions to be listed as either RV32 or RV64 only, allowing
these opcodes to overlap.
- The C backend has been modifed to emit the "DECLARE_RV32_ONLY" or
"DECLARE_RV64_ONLY" macros as needed.
- The other backends have not been modified, and may need to be in the
future.
On branch scalar-crypto
Changes to be committed:
modified: Makefile
new file: opcodes-rv32k
new file: opcodes-rv64k
new file: opcodes-rvk
modified: parse_opcodes
|
