Ben Marshall

Following up on this - after getting the arch-review feedback and discussing it at the 22/Jul/21 TG meeting, we decided _not_ to overlap the aes32 and aes64 opcodes. You can...

For those that the news hasn't filtered out too yet - K is the designation for the cryptography extension...

I'm happy adding a note to the synopsis to each instruction if that'd make things clearer. These instructions & their names were originally defined by the bitmanip task group so...

For the sake of keeping as much information in one place as possible... There have been numerous prior discussions on this issue long before we hit public review. As a...

> encoding did not directly support the preferred and customary use of the instructions. Unless I'm misunderstanding, I'm not sure this is true. The current encoding _does_ support the expected...

I've tried to capture all of this in an [update](https://github.com/riscv/riscv-crypto/commit/e4fd6e20b365db8cf9e3b02048fd312d2fb76576) to the [public review summary](https://github.com/riscv/riscv-crypto/blob/master/doc/scalar/public-review-summary.adoc). I couldn't capture _everything_ you've written, so have linked to this issue and tried to...

I agree this is a nice to have. I don't know how Bitmanip generated these diagrams. I used the script in `bin/better-parse-opcodes.py`. So some modifications to that might do the...

I think this sort of change is hard to make now the specification is frozen unless a very good case for it can be made. I appreciate the encodings don't...

Hi @JamesKenneyImperas I think you've captured something which has been looming for a while. I agree that the benchmarks could do with - A general tidyup of the source code...

Nice catch! Thank you, I will update this in the spec when I have some time on Wednesday. You're absolutely right about how it was a typo, I must have...