-
Notifications
You must be signed in to change notification settings - Fork 5.3k
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
8318895: Deoptimization results in incorrect lightweight locking stack #16568
Conversation
👋 Welcome back rkennke! A progress list of the required criteria for merging this PR into |
Webrevs
|
/contributor add @xmas92 |
@rkennke |
@rkennke 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 26 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 |
Hi Roman, thanks for opening the pr. I've implemented another test case that demonstrates why relocking should be done before an object reference with eliminated locking is passed to a JVMTI agent. Would it be ok to include it in your pr? I will put the change through our CI testing. Cheers, Richard. |
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.
Fix and new test case look good to me.
Local testing was clean.
Thanks, Richard.
Co-authored-by: Richard Reingruber <richard.reingruber@sap.com>
/contributor add @reinrich |
@rkennke |
Thanks, all! /integrate |
Going to push as commit ea1ffa3.
Your commit was automatically rebased without conflicts. |
There may be an issue here but it is pre-existing (at least to some extent). |
See JBS issue for details.
I basically:
Testing:
Progress
Issue
Reviewers
Contributors
<aboldtch@openjdk.org>
<rrich@openjdk.org>
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/16568/head:pull/16568
$ git checkout pull/16568
Update a local copy of the PR:
$ git checkout pull/16568
$ git pull https://git.openjdk.org/jdk.git pull/16568/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 16568
View PR using the GUI difftool:
$ git pr show -t 16568
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/16568.diff
Webrev
Link to Webrev Comment