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
8253183: Fragile memory barrier selection for some weak memory model platforms #387
Conversation
👋 Welcome back mdoerr! A progress list of the required criteria for merging this PR into |
@TheRealMDoerr The following label will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command. |
Webrevs
|
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.
Hi Martin,
This looks good as was previously discussed.
Thanks,
David
@TheRealMDoerr 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 more 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 23 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 |
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. Thanks for taking care of this Martin.
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.
Thumbs up! Your call on whether to switch from 'iriw' to 'IRIW'
in the new function name.
// Processors which are not multi-copy-atomic require a full fence | ||
// to enforce a globally consistent order of Independent Reads of | ||
// Independent Writes. Please use only for such patterns! | ||
static void loadload_for_iriw() { |
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.
So why is this (lower case) 'iriw' when we almost always
talk about it as IRIW?
|
||
// _contentions and dmw/header may get written by different threads. | ||
// Make sure to observe them in the same order when having several observers. | ||
OrderAccess::loadload_for_iriw(); |
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 code we are replacing used 'IRIW' instead of 'iriw'.
|
||
// dmw/header and _contentions may get written by different threads. | ||
// Make sure to observe them in the same order when having several observers. | ||
OrderAccess::loadload_for_iriw(); |
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 code we're replacing using 'IRIW' instead of 'iriw'.
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.
Makes sense. Renamed to upper case IRIW. Also removed unnecessary OrderAccess:: qualification inside of class OrderAccess.
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.
Thanks for making those changes. Thumbs up.
/integrate |
@TheRealMDoerr Since your change was applied there have been 32 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit dc3a0f5. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Hi, I'd like to propose a fix after the discussion in https://bugs.openjdk.java.net/browse/JDK-8253183
Please especially review my new comments in the code. The authors of the surrounding code in objectMonitor.cpp and synchronizer.cpp may know better.
Progress
Issue
Reviewers
Download
$ git fetch https://git.openjdk.java.net/jdk pull/387/head:pull/387
$ git checkout pull/387