-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
8273489: Zero: Handle UseHeavyMonitors on all monitorenter paths #5416
Conversation
👋 Welcome back shade! A progress list of the required criteria for merging this PR into |
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.
@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 49 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 |
Thanks! I'll integrate now. /integrate |
Going to push as commit e3bda63.
Your commit was automatically rebased without conflicts. |
While fixing JDK-8273486, I noticed there is one place where we do not call VM slowpath when
UseHeavyMonitors
are requested. That place isZeroInterpreter::native_entry
. We should probably implementUseHeavyMonitors
check on those paths.New code is modeled after existing uses, for example this.
Additional testing:
make bootcycle-images
make bootcycle-images
with-XX:+UseHeavyMonitors
forcedProgress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/5416/head:pull/5416
$ git checkout pull/5416
Update a local copy of the PR:
$ git checkout pull/5416
$ git pull https://git.openjdk.java.net/jdk pull/5416/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 5416
View PR using the GUI difftool:
$ git pr show -t 5416
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/5416.diff