[Intrinsics] Fix incorrect _vxarq_u64 intrisic
#1222
Merged
Conversation
This file contains hidden or 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
franziskuskiefer
approved these changes
Nov 3, 2025
Member
franziskuskiefer
left a comment
franziskuskiefer
left a comment
There was a problem hiding this comment.
Thanks!
We should make a release with this
|
Is there an advisory/analysis of this bug? What are the implications and security impact? |
Collaborator
Author
Thank you for creating rustsec/advisory-db#2493. We've replied there with a suggestion for the advisory text. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
The manual implementation of
vxarq_u64for platforms where that intrisic isn't available was using the wrong input for one of the shift operands.This PR also adds Linux ARM64 runners to the build & test matrices for ML-DSA and ML-KEM CI.