-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8374785: Template Library: need to tag Float16.copySign as having non-deterministic result because of multiple NaNs with different sign bits #29118
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
Conversation
|
👋 Welcome back epeter! A progress list of the required criteria for merging this PR into |
|
@eme64 This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be: You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 82 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. ➡️ To integrate this PR with the above commit message to the |
TobiHartmann
left a comment
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.
Looks good to me.
|
@merykitty @TobiHartmann Thanks for the reviews! /integrate |
|
Going to push as commit 2fbe475.
Your commit was automatically rebased without conflicts. |
This is a very similar issue as #29033 / JDK-8374489.
There are
NaNencodings that have the sign bit set, and others that have it not set.If we now copy the sign from such a
NaNto a numeric value (e.g.1), we can get1or-1.Since
NaNvalues of different encodings are interchangable, and we cannot know whatNaNwe get, and hence the sign bit is arbitrary, we can also not know the sign of the result ofFloat16.copySign. We have to mark it as non-deterministic and hence disable result verification.Since this is a test-bug, I have no regression test. But I verified it manually, that with the same seed (for the ExpressionFuzzer) that fails before this change, we now succeed after the change.
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/29118/head:pull/29118$ git checkout pull/29118Update a local copy of the PR:
$ git checkout pull/29118$ git pull https://git.openjdk.org/jdk.git pull/29118/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 29118View PR using the GUI difftool:
$ git pr show -t 29118Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/29118.diff
Using Webrev
Link to Webrev Comment