Skip to content

8354383: C2: enable sinking of Type nodes out of loop#25396

Closed
rwestrel wants to merge 4 commits intoopenjdk:masterfrom
rwestrel:JDK-8354383
Closed

8354383: C2: enable sinking of Type nodes out of loop#25396
rwestrel wants to merge 4 commits intoopenjdk:masterfrom
rwestrel:JDK-8354383

Conversation

@rwestrel
Copy link
Contributor

@rwestrel rwestrel commented May 22, 2025

PhaseIdealLoop::try_sink_out_of_loop() excludes Type nodes because
we ran into some issues where a Type node is sunk and then becomes
top but the control path of its uses doesn't become unreachable.

8349479 should have fixed that so that exception no longer makes
sense.


Progress

  • Change must be properly reviewed (1 review required, with at least 1 Reviewer)
  • Change must not contain extraneous whitespace
  • Commit message must refer to an issue

Issue

  • JDK-8354383: C2: enable sinking of Type nodes out of loop (Enhancement - P4)

Reviewers

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/25396/head:pull/25396
$ git checkout pull/25396

Update a local copy of the PR:
$ git checkout pull/25396
$ git pull https://git.openjdk.org/jdk.git pull/25396/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 25396

View PR using the GUI difftool:
$ git pr show -t 25396

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/25396.diff

Using Webrev

Link to Webrev Comment

@bridgekeeper
Copy link

bridgekeeper bot commented May 22, 2025

👋 Welcome back roland! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

@openjdk
Copy link

openjdk bot commented May 22, 2025

@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:

8354383: C2: enable sinking of Type nodes out of loop

Reviewed-by: chagedorn, thartmann

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 371 new commits pushed to the master branch:

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 master branch, type /integrate in a new comment.

@openjdk openjdk bot added the rfr Pull request is ready for review label May 22, 2025
@openjdk
Copy link

openjdk bot commented May 22, 2025

@rwestrel The following label will be automatically applied to this pull request:

  • hotspot-compiler

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.

@openjdk openjdk bot added the hotspot-compiler hotspot-compiler-dev@openjdk.org label May 22, 2025
@mlbridge
Copy link

mlbridge bot commented May 22, 2025

Webrevs

Copy link
Member

@TobiHartmann TobiHartmann left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That looks good to me but given that we had quite a few bugs in that area in the past, I would suggest to only integrate into JDK 26 after the fork on June 05, 2025.

@openjdk openjdk bot added the ready Pull request is ready to be integrated label May 23, 2025
Copy link
Member

@chhagedorn chhagedorn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Otherwise, looks reasonable to me, too.

!n->is_OpaqueNotNull() &&
!n->is_OpaqueInitializedAssertionPredicate() &&
!n->is_OpaqueTemplateAssertionPredicate() &&
!n->is_Type()) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I cannot remember exactly, how often was it a problem without JDK-8349479? If it was more common, we might want to only allow it when KillPathsReachableByDeadTypeNode is set.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I made that change.
As far as I remember, the logic removed by JDK-8319372 played a key role in those failures. Not sure if any were still reproducible after than one.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, that matches what I remember. Maybe JDK-8319372 can now be reverted with JDK-8349479 in?

@rwestrel
Copy link
Contributor Author

That looks good to me but given that we had quite a few bugs in that area in the past, I would suggest to only integrate into JDK 26 after the fork on June 05, 2025.

Sounds reasonable to me.

@openjdk openjdk bot removed the ready Pull request is ready to be integrated label May 26, 2025
!n->is_OpaqueNotNull() &&
!n->is_OpaqueInitializedAssertionPredicate() &&
!n->is_OpaqueTemplateAssertionPredicate() &&
!n->is_Type()) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, that matches what I remember. Maybe JDK-8319372 can now be reverted with JDK-8349479 in?

@openjdk openjdk bot added the ready Pull request is ready to be integrated label May 26, 2025
Co-authored-by: Christian Hagedorn <christian.hagedorn@oracle.com>
@rwestrel
Copy link
Contributor Author

Maybe JDK-8319372 can now be reverted with JDK-8349479 in?

I think it would be safe but I'm unclear if it's worth doing or not.

@openjdk openjdk bot removed the ready Pull request is ready to be integrated label May 26, 2025
@chhagedorn
Copy link
Member

I'm not sure either, we would not to further investigate if we can find cases that benefit from it. Should we file an RFE either way?

@rwestrel
Copy link
Contributor Author

rwestrel commented Jun 3, 2025

I'm not sure either, we would not to further investigate if we can find cases that benefit from it. Should we file an RFE either way?

I filed: https://bugs.openjdk.org/browse/JDK-8358501

@openjdk openjdk bot added the ready Pull request is ready to be integrated label Jun 10, 2025
@rwestrel
Copy link
Contributor Author

@TobiHartmann @chhagedorn thanks for the reviews.

@rwestrel
Copy link
Contributor Author

/integrate

@openjdk
Copy link

openjdk bot commented Jun 10, 2025

Going to push as commit a2f99fd.
Since your change was applied there have been 373 commits pushed to the master branch:

Your commit was automatically rebased without conflicts.

@openjdk openjdk bot added the integrated Pull request has been integrated label Jun 10, 2025
@openjdk openjdk bot closed this Jun 10, 2025
@openjdk openjdk bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review labels Jun 10, 2025
@openjdk
Copy link

openjdk bot commented Jun 10, 2025

@rwestrel Pushed as commit a2f99fd.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

hotspot-compiler hotspot-compiler-dev@openjdk.org integrated Pull request has been integrated

Development

Successfully merging this pull request may close these issues.

3 participants