-
Notifications
You must be signed in to change notification settings - Fork 6.1k
8358334: C2/Shenandoah: incorrect execution with Unsafe #25729
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 roland! A progress list of the required criteria for merging this PR into |
@rwestrel 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 129 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 |
@rwestrel The |
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.
LGTM. Thanks.
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.
Thank you for this!
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.
The patch makes sense.
I ran make test TEST=all TEST_VM_OPTS=-XX:+UseShenandoahGC
without new failures.
@JohnTortugo @earthling-amzn @shipilev thanks for the reviews and testing. |
/integrate |
Going to push as commit 1fcede0.
Your commit was automatically rebased without conflicts. |
When a barrier is expanded, some control is picked as a location for
the barrier. The control input of data nodes that depend on that
control are updated so the nodes are after the expanded barrier unless
the barrier itself depends on some of those nodes.
In this particular failure, a raw memoy
Store
is the input memory tothe barrier. That
Store
has an anti-dependentLoad
. All 3 nodes(barrier,
Load
andStore
) are at the same control. TheStore
isan input to the barrier so it stays before the barrier. The
Load
'scontrol is updated to be after the barrier which breaks the
anti-dependency. The bug is that the logic that sorts nodes that need
to be before the barrier and those that can be after ignores
anti-dependencies. The fix simply extends that logic to take them into
account.
/cc shenandoah,hotspot-compiler
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/25729/head:pull/25729
$ git checkout pull/25729
Update a local copy of the PR:
$ git checkout pull/25729
$ git pull https://git.openjdk.org/jdk.git pull/25729/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 25729
View PR using the GUI difftool:
$ git pr show -t 25729
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/25729.diff
Using Webrev
Link to Webrev Comment