Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

require Zvkt in RVA23 #136

Merged
merged 1 commit into from
Dec 11, 2023
Merged

require Zvkt in RVA23 #136

merged 1 commit into from
Dec 11, 2023

Conversation

oconnor663
Copy link
Contributor

Closes #133. There hasn't been any discussion there, so I don't know if this change is actually wanted, but I wanted to make it as easy as possible for someone to click the merge button if so :) Here's a copy of the body of that issue:

RVA23 currently mandates both Zkt and V, so it seems natural that it should also mandate Zvkt. Although the optional Zvkng and Zvksg extensions both imply Zvkt, high-performance implementations of a lot of software-oriented cryptography primitives (like ChaCha and Poly1305) depend only on V and Zvbb, and those implementations are likely to assume Zvkt even if it's not officially required.

@oconnor663 oconnor663 changed the title RVA23 requires Zvkt require Zvkt in RVA23 Dec 10, 2023
Copy link
Member

@aswaterman aswaterman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm pretty sure this is what's intended, so I'll go ahead and merge it. If there are dissenting voices, feel free to open a new issue.

@aswaterman aswaterman merged commit 7fa2994 into riscv:main Dec 11, 2023
1 check passed
@oconnor663 oconnor663 deleted the require_zvkt branch December 11, 2023 04:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Should RVA23 mandate Zvkt?
2 participants