-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8272446 C1: Raw version of UnsafeGet generates load barriers #5109
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
8272446 C1: Raw version of UnsafeGet generates load barriers #5109
Conversation
|
👋 Welcome back stefank! A progress list of the required criteria for merging this PR into |
Webrevs
|
fisk
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.
|
@stefank 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 no new commits pushed to the ➡️ To integrate this PR with the above commit message to the |
veresov
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.
|
/integrate |
|
Going to push as commit df1427b.
Your commit was automatically rebased without conflicts. |
Please review this patch to remove load barriers from the "raw" version of UnsafeGet.
After rebasing the ZGC Generational code to latest openjdk/jdk we hit a crash because a load barrier was generated for some oops that are not supposed to have a load barrier. In upstream ZGC this isn't a problem because these load barriers are just redundant and will find healed good oops. However, in the Generational version un-barriered roots (e.g. thread stacks) have no metadata bits, and we should never perform normal load barriers on them (they are handled by stack watermarks and nmethod barriers).
This load barrier was introduced with:
JDK-8266746: C1: Replace UnsafeGetRaw with UnsafeGet when setting up OSR entry block
which makes UnsafeGet also handle "raw" loads. However, the "raw" path introduced a load barrier. Note that "raw" is often used to denote a function that loads/stores values without using a barrier.
I've tested this with tier1-3 and have had some initial set of eyes looking over the patch, but it would be good to scrutinize this patch and the usage of UnsafeGet in GraphBuilder::setup_osr_entry_block.
@TheRealMDoerr could you check if this patch works with PPC?
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/5109/head:pull/5109$ git checkout pull/5109Update a local copy of the PR:
$ git checkout pull/5109$ git pull https://git.openjdk.java.net/jdk pull/5109/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 5109View PR using the GUI difftool:
$ git pr show -t 5109Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/5109.diff