-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
8297951: C2: Create skeleton predicates for all If nodes in loop predication #11454
Conversation
👋 Welcome back chagedorn! A progress list of the required criteria for merging this PR into |
@chhagedorn 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. |
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 reasonable to me. Great that you were able to find a test!
@chhagedorn 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 240 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 Tobias for your 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.
Make sense.
Thank you Vladimir for your review! |
/integrate |
Going to push as commit 0bd04a6.
Your commit was automatically rebased without conflicts. |
@chhagedorn Pushed as commit 0bd04a6. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
We currently only create skeleton predicates for
RangeCheck
nodes and not for normalIf
nodes:jdk/src/hotspot/share/opto/loopPredicate.cpp
Lines 1344 to 1346 in 2cb64a7
But it is also possible to create range check predicates in loop predication for
If
nodes if they have the right pattern checked inPhaseIdealLoop::loop_predication_impl()
andIdealLoopTree::is_range_check_if()
. This, however, is much more rare.Without skeleton predicates for these
If
nodes, we could run into the same problems already fixed forRangeCheck
nodes (see JDK-8193130 and related bugs). This is almost impossible to trigger in practice as it needs a very specific setup and the right optimizations to be applied. But the test case shows such a case where we hit an assert due to a broken memory graph because we are missing skeleton predicates.I therefore propose to always create skeleton predicates for hoisted range checks in loop predication.
Thanks,
Christian
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk pull/11454/head:pull/11454
$ git checkout pull/11454
Update a local copy of the PR:
$ git checkout pull/11454
$ git pull https://git.openjdk.org/jdk pull/11454/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 11454
View PR using the GUI difftool:
$ git pr show -t 11454
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/11454.diff