-
Notifications
You must be signed in to change notification settings - Fork 5.8k
8273277: C2: Move conditional negation into rc_predicate #5987
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 neliasso! A progress list of the required criteria for merging this PR into |
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.
I do have a concern that negating the condition of the rangecheck in the skeleton predicate, since the skeleton predicate will be used as a clone template, and some rangechecks optimizations seems to assume that range checks always have LT as the condidtion. On the other hand - it is a really uncommon scenario since we haven't failed here before.
Is there any specific code that you worry about?
I think it should be fine because the purpose of copying and instantiating skeleton range check predicates is to guarantee that control/data paths die consistently when the main loop induction variable falls outside of the allowed range of an array access. But @rwestrel and @chhagedorn looked more into this recently.
Can we add the test that Tencent found as well?
Please update the affects versions in the bug report.
I have seen checks for LT, but I see none that specifically would be affecting this change.
Yes - I've added it.
Done. |
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.
* @test | ||
* @bug 8273277 | ||
* @summary Skeleton predicates sometimes need to be negated | ||
* @run main compiler.loopopts.TestSkeletonPredicateNegation |
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.
I think this should be changed to @run driver
.
} | ||
} | ||
|
||
public void mainTest (String[] args){ |
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.
Code style should be mainTest(String[] args) {
@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 341 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 |
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.
That looks reasonable to me.
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.
I agree.
/integrate |
Going to push as commit 710f496.
Your commit was automatically rebased without conflicts. |
Hi,
I need some feedback on this patch. This was reported from Tencent and found in internal testing about the same time. This patch is based on a a patch provided by Tencent.
In some very specific circumstances we need to negate the range checks that we create in PhaseIdealLoop::loop_predication_impl_helper. This is done in three places, but that method also calls insert_initial_skeleton_predicate where this isn't taken into account.
To simplify things I have moved the negation logic into rc_predicate. This should prevent us from missing this check again.
I do have a concern that negating the condition of the rangecheck in the skeleton predicate, since the skeleton predicate will be used as a clone template, and some rangechecks optimizations seems to assume that range checks always have LT as the condidtion. On the other hand - it is a really uncommon scenario since we haven't failed here before.
Feedback appreciated.
Best regards,
Nils
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/5987/head:pull/5987
$ git checkout pull/5987
Update a local copy of the PR:
$ git checkout pull/5987
$ git pull https://git.openjdk.java.net/jdk pull/5987/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 5987
View PR using the GUI difftool:
$ git pr show -t 5987
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/5987.diff