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
8262298 : G1BarrierSetC2::step_over_gc_barrier fails with assert "bad barrier shape" #3029
Conversation
👋 Welcome back neliasso! A progress list of the required criteria for merging this PR into |
/label add hotspot-compiler |
@neliasso |
@neliasso |
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.
Will the barrier be eliminated eventually in this case?
@neliasso 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 54 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 |
Yes - it will disappear in the same igvn pass. Thanks for the review! |
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 the review! |
/integrate |
@neliasso Since your change was applied there have been 56 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit cdf78e4. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
During eliminate_macro_nodes an allocation and a tightly coupled arraycopy is eliminated. The gc barrier is still there but the entry condition is always false. During the subsequent igvn we can hit an assert depending on what order the barrier nodes are removed.
If the entry to the gc barrier is removed first - the exit region node will have Parm-control as in(2). This is a sign that it is a barrier during teardown. I add a check for that in this patch.
Progress
Issue
Reviewers
Download
To checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/3029/head:pull/3029
$ git checkout pull/3029
To update a local copy of the PR:
$ git checkout pull/3029
$ git pull https://git.openjdk.java.net/jdk pull/3029/head