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.
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
Implement fcvt_to_uint_sat (f32x4 -> i32x4) for x86 #1822
Implement fcvt_to_uint_sat (f32x4 -> i32x4) for x86 #1822
Changes from all commits
7dad5e2
192ea42
519e63e
229ed9d
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are the rounding semantics of the two alternative implementations equivalent? For the short case,
vcvtps2udq
, the Intel manual says "When a conversion is inexact, the value returned is rounded according to the rounding control bits in the MXCSR register or the embedded rounding control bits." The slow path appears to usecvtt2si
(presumably, really,cvttps2pi
), and all thett
variant conversion insns are round-towards-zero: "When a conversion is inexact, a truncated (round toward zero) result is returned."There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a good point: I had hoped MXCSR would have the right rounding mode but it does not. I added a
run
filetest that passes with the long sequence and fails with the AVX512 sequence: it looks like the machines running the CI have AVX512 and therefore fail. I started playing around with a new recipe that embeds the rounding control (e.g.EvexContext::RoundingRegToRegFP { rc: EvexRoundingControl::RZ }
but this didn't immediately fix the test case (the emitted bytes aren't exactly right) so I will have to play around with this a bit more.