-
Notifications
You must be signed in to change notification settings - Fork 6.1k
8335977: Deoptimization fails with assert "object should be reallocated already" #21624
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 cslucas! A progress list of the required criteria for merging this PR into |
@JohnTortugo 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 242 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. As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@TobiHartmann, @iwanowww, @vnkozlov) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
@JohnTortugo 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.
The fix looks good to me.
Now that the -XX:+StressUnstableIfTraps
option was added with JDK-8335334, could you please also add Test.java that I used originally to reproduce the issue?
Does your test also reproduce the NPE example that @chhagedorn triggered with his Test3.java? If not, I think that one should be added as well.
The more tests we have for this, the better :)
test/hotspot/jtreg/compiler/escapeAnalysis/TestReduceAllocationAndJVMStates.java
Outdated
Show resolved
Hide resolved
I executed some extended testing. All green. |
The test I added in this PR is based on @chhagedorn Test3.java. I was able to reproduce the issue on my end fairly easily.
I wasn't able to reproduce the issue using Test.java, how often does it reproduce for you with the flags that you listed at the top of Test.java ? Thanks for testing @TobiHartmann ! |
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.
Ah right, all good then. Please add @chhagedorn as co-contributor since he extracted that test.
Right, I just tried and it does not seem to reproduce anymore. Too bad but let's leave it out then. |
/contributor add @chhagedorn |
@JohnTortugo |
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 to me too.
/integrate |
@JohnTortugo This pull request has not yet been marked as ready for integration. |
/integrate |
@JohnTortugo |
/sponsor |
Going to push as commit 7d8bd21.
Your commit was automatically rebased without conflicts. |
@vnkozlov @JohnTortugo Pushed as commit 7d8bd21. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Please, review this patch to fix an issue that may occur when serializing debug information related to reduce allocation merges. The problem happens when there are more than one JVMS in a
uncommon_trap
and a younger JVMS doesn't have the RAM inputs as a local/expression/monitor but an older JVMS does. In that situation the loop at line 1173 of output.cpp will set theis_root
property of the ObjectValue tofalse
when processing the younger JVMS even though it may have been set totrue
when visiting the older JVMS.Tested on:
Progress
Issue
Reviewers
Contributors
<chagedorn@openjdk.org>
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/21624/head:pull/21624
$ git checkout pull/21624
Update a local copy of the PR:
$ git checkout pull/21624
$ git pull https://git.openjdk.org/jdk.git pull/21624/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 21624
View PR using the GUI difftool:
$ git pr show -t 21624
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/21624.diff
Using Webrev
Link to Webrev Comment