-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
8315377: C2: assert(u->find_out_with(Op_AddP) == nullptr) failed: more than 2 chained AddP nodes? #15562
Conversation
👋 Welcome back roland! A progress list of the required criteria for merging this PR into |
4edab23
to
8eebf75
Compare
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!
@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 182 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.
Looks good to me too.
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.
@chhagedorn @vnkozlov @TobiHartmann thanks for the reviews. |
/integrate |
Going to push as commit ba1a463.
Your commit was automatically rebased without conflicts. |
PhaseIdealLoop::try_sink_out_of_loop()
has special logic to handleAddP
nodes so, after it has been processed, all nodes in the chainof
AddP
nodes still have the same base input. That logic assumes achain is only composed of at most 2 nodes. That's not true because
PhaseIdealLoop::remix_address_expressions()
can cause longer chainsto exist. There's actually no clear upper bound on the number of nodes
in such a chain. The fix I propose here is simply to extend the logic
in
PhaseIdealLoop::try_sink_out_of_loop()
to handle arbitrarychains.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/15562/head:pull/15562
$ git checkout pull/15562
Update a local copy of the PR:
$ git checkout pull/15562
$ git pull https://git.openjdk.org/jdk.git pull/15562/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 15562
View PR using the GUI difftool:
$ git pr show -t 15562
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/15562.diff
Webrev
Link to Webrev Comment