-
Notifications
You must be signed in to change notification settings - Fork 5.8k
8350329: C2: Div looses dependency on condition that guarantees divisor not zero in counted loop after peeling #25262
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
base: master
Are you sure you want to change the base?
Conversation
👋 Welcome back roland! A progress list of the required criteria for merging this PR into |
@rwestrel 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 44 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 |
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.
Looks good to me.
* @run main/othervm -XX:-TieredCompilation -XX:-BackgroundCompilation -XX:-UseLoopPredicate -XX:+StressGCM -XX:StressSeed=31780379 TestPeeledLoopNoBackedgeFloatingDiv | ||
* @run main/othervm -XX:-TieredCompilation -XX:-BackgroundCompilation -XX:-UseLoopPredicate -XX:+StressGCM TestPeeledLoopNoBackedgeFloatingDiv |
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.
You should use -XX:+UnlockDiagnosticVMOptions
for StressGCM
and maybe also add -XX:+IgnoreUnrecognizedVMOptions
when run without C2 since UseLoopPredicate
is a C2 only flag.
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.
Thanks for reviewing this. Done in the new commit.
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.
This is an issue similar to 8349139: the type of the iv phi of a
counted loop is narrowed down so a
Div
node doesn't need a controlinput. The loop is then peeled. The
Div
in the loop body isguaranteed to be non zero only if it is actually executed so the
Div
is implicitly dependent on the zero trip guard. Then the loop looses
its backedge and the
Div
freely floats. TheDiv
instruction isscheduled above the zero trip guard and faults. Had the
Div
beencontrol dependent on the zero trip guard, it wouldn't have
executed. The fix, similar to 8349139 is to add a
CastII
on peelingto make the dependency between what's in the loop body and relies on
the narrowed down type of the iv phi and the zero trip guard explicit.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/25262/head:pull/25262
$ git checkout pull/25262
Update a local copy of the PR:
$ git checkout pull/25262
$ git pull https://git.openjdk.org/jdk.git pull/25262/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 25262
View PR using the GUI difftool:
$ git pr show -t 25262
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/25262.diff
Using Webrev
Link to Webrev Comment