-
Notifications
You must be signed in to change notification settings - Fork 232
8351997: AArch64: Interpreter volatile reference stores with G1 are not sequentially consistent #3697
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
8351997: AArch64: Interpreter volatile reference stores with G1 are not sequentially consistent #3697
Conversation
|
👋 Welcome back shade! A progress list of the required criteria for merging this PR into |
|
@shipilev 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 4 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 |
|
This backport pull request has now been updated with issue from the original commit. |
|
/approval request Same reason as for 21u. Same level of testing is performed; jcstress now passes. Similar risk to 21u: while the patch is relatively new, it is well understood. |
|
@shipilev |
Well, that's odd. Looks like @theRealAph approved the backport before I asked for the approval :) Was that intentional, Andrew? I'll put |
Oh, sorry. I was going to review it, and then I thought to myself that maintainers are rarer than approvers, so it's a better bottleneck to do the approval. I never thought to check you'd asked. I'm not sure that requiring an ask before approval is granted is more than process for its own sake anyway. |
Yeah, I followed the process: submit the PR, let people look at it while testing is running, wait until testing is complete, use test results as the justification for backport. So there is a natural sequence of events here :) Anyhow, I need a formal Review in this PR, as Erik's "committer" review formally does not count. |
adinn
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.
Yep, nod it through . . .
|
Thanks, here we go. /integrate |
|
Going to push as commit 0e9b1df.
Your commit was automatically rebased without conflicts. |
Fixes AArch64 memory ordering problem. Readily manifests in new jcstress tests; there are sightings of related problems in JSR 133 tests.
The patch is not clean, because JDK-8301996 is in the way, and it is IMO too risky to backport. I picked up the JDK 21u backport version (https://git.openjdk.org/jdk21u-dev/commit/729f10053eab4b8fe8a857e14ce0f96a82c721b8), where I resolved some hunks to match the intended behavior, after checking
do_oop_storeclobbers the samer3as in mainline.Additional testing:
RefDekkertest now passesseqcst.volatiles.reftests now passalltests now passallProgress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk17u-dev.git pull/3697/head:pull/3697$ git checkout pull/3697Update a local copy of the PR:
$ git checkout pull/3697$ git pull https://git.openjdk.org/jdk17u-dev.git pull/3697/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 3697View PR using the GUI difftool:
$ git pr show -t 3697Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk17u-dev/pull/3697.diff
Using Webrev
Link to Webrev Comment