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.
Apply random float error #4156
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
Apply random float error #4156
Changes from all commits
f5330d0
5c9eaa3
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.
@RalfJung Is this really allowed behavior for the algebraic intrinsics? From the documentation for
fadd_algebraic
"Float addition that allows optimizations based on algebraic rules." I would assume that this should either evaluatea + b
orb + a
, but not introduce random errors.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.
Yes it is. Note that
a + b
andb + a
produce identical results even for floats, so that optimization can be performed without the program even noticing, and happens even when you do not use the intrinsics. The intrinsic also allows things like associativity and distributivity, which can change the results -- and there's no good way to put any bounds on how it changes the results.This is a closed PR, not a venue for discussion. If you have further questions, please open a thread on the forum.
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.
Note that the docs even call this out:
Anything beyond "returns an arbitrary random float" is a quality-of-implementation concern, not a stable guarantee unsafe code can rely on.