-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8374489: Template Library: need to tag Float16.float16ToRawShortBits as having non-deterministic result because of multiple NaN bit patterns #29033
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 6 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 |
chhagedorn
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 and trivial!
vnkozlov
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.
Good.
|
@vnkozlov @chhagedorn Thanks for the reviews! /integrate |
|
Going to push as commit 2cb228e.
Your commit was automatically rebased without conflicts. |
In JDK-8370922, I added Float16 support to the Template Library. I missed to tag Float16.float16ToRawShortBits as having non-deterministic result.
We need to do that, just like for float and double equivalents:
Arithmetic operations (e.g. add, mul, fma, ...) are allowed to pick either input if it gets two NaNs of different bit patterns.
That way, those operations can generate different NaN bit patterns depending on if we use interpreter/C1/C2.
If we now convert to raw bits, we get different bits, and would wrongly conclude that we get a wrong result.
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/29033/head:pull/29033$ git checkout pull/29033Update a local copy of the PR:
$ git checkout pull/29033$ git pull https://git.openjdk.org/jdk.git pull/29033/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 29033View PR using the GUI difftool:
$ git pr show -t 29033Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/29033.diff
Using Webrev
Link to Webrev Comment