Skip to content

8373524: C2: no reachable node should have no use#28841

Closed
rwestrel wants to merge 8 commits intoopenjdk:masterfrom
rwestrel:JDK-8373524
Closed

8373524: C2: no reachable node should have no use#28841
rwestrel wants to merge 8 commits intoopenjdk:masterfrom
rwestrel:JDK-8373524

Conversation

@rwestrel
Copy link
Contributor

@rwestrel rwestrel commented Dec 16, 2025

The failure occurs because PhiNode::Ideal uses set_req to update
an input of a Phi. That causes the previous input to be disconnected
but because of the use of set_req, the previous input that has no
use is not enqueued for igvn to be reclaimed. The fix is to use
set_req_X instead. I replaced uses of set_req with set_req_X in
PhiNode::Ideal where I thought it made 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-8373524: C2: no reachable node should have no use (Bug - P3)(⚠️ The fixVersion in this issue is [26] but the fixVersion in .jcheck/conf is 27, a new backport will be created when this pr is integrated.)

Reviewers

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 28841

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

Using diff file

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

Using Webrev

Link to Webrev Comment

@bridgekeeper
Copy link

bridgekeeper bot commented Dec 16, 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 Dec 16, 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:

8373524: C2: no reachable node should have no use

Reviewed-by: chagedorn, mhaessig

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 71 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 hotspot-compiler hotspot-compiler-dev@openjdk.org label Dec 16, 2025
@openjdk
Copy link

openjdk bot commented Dec 16, 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 rfr Pull request is ready for review label Dec 16, 2025
@mlbridge
Copy link

mlbridge bot commented Dec 16, 2025

Webrevs

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 good!

@@ -0,0 +1,88 @@
/*
Copy link
Member

Choose a reason for hiding this comment

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

Since this is about IGVN, you could move the test to compiler/igvn.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Right. That makes sense. Done in the new commits.

@openjdk openjdk bot added the ready Pull request is ready to be integrated label Dec 17, 2025
Copy link
Contributor

@mhaessig mhaessig left a comment

Choose a reason for hiding this comment

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

Thank you for fixing this, @rwestrel. The changes look good. I also kicked off some testing.

rwestrel and others added 2 commits December 17, 2025 15:04
Co-authored-by: Christian Hagedorn <christian.hagedorn@oracle.com>
…java

Co-authored-by: Christian Hagedorn <christian.hagedorn@oracle.com>
@openjdk openjdk bot removed the ready Pull request is ready to be integrated label Dec 17, 2025
Copy link
Contributor

@mhaessig mhaessig left a comment

Choose a reason for hiding this comment

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

Testing passed and the new changes look good as well.

@rwestrel
Copy link
Contributor Author

@chhagedorn @mhaessig thanks for the reviews and testing.

@rwestrel
Copy link
Contributor Author

/integrate

@openjdk
Copy link

openjdk bot commented Dec 18, 2025

@rwestrel This pull request has not yet been marked as ready for integration.

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.

Update looks good, thanks!

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

@chhagedorn thanks for re-approving.

@rwestrel
Copy link
Contributor Author

/integrate

@openjdk
Copy link

openjdk bot commented Dec 19, 2025

Going to push as commit e72f205.
Since your change was applied there have been 71 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 Dec 19, 2025
@openjdk openjdk bot closed this Dec 19, 2025
@openjdk openjdk bot removed the ready Pull request is ready to be integrated label Dec 19, 2025
@openjdk openjdk bot removed the rfr Pull request is ready for review label Dec 19, 2025
@openjdk
Copy link

openjdk bot commented Dec 19, 2025

@rwestrel Pushed as commit e72f205.

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

@rwestrel
Copy link
Contributor Author

rwestrel commented Jan 5, 2026

/backport :jdk26

@openjdk
Copy link

openjdk bot commented Jan 5, 2026

@rwestrel the backport was successfully created on the branch backport-rwestrel-e72f205a-jdk26 in my personal fork of openjdk/jdk. To create a pull request with this backport targeting openjdk/jdk:jdk26, just click the following link:

➡️ Create pull request

The title of the pull request is automatically filled in correctly and below you find a suggestion for the pull request body:

Hi all,

This pull request contains a backport of commit e72f205a from the openjdk/jdk repository.

The commit being backported was authored by Roland Westrelin on 19 Dec 2025 and was reviewed by Christian Hagedorn and Manuel Hässig.

Thanks!

If you need to update the source branch of the pull then run the following commands in a local clone of your personal fork of openjdk/jdk:

$ git fetch https://github.com/openjdk-bots/jdk.git backport-rwestrel-e72f205a-jdk26:backport-rwestrel-e72f205a-jdk26
$ git checkout backport-rwestrel-e72f205a-jdk26
# make changes
$ git add paths/to/changed/files
$ git commit --message 'Describe additional changes made'
$ git push https://github.com/openjdk-bots/jdk.git backport-rwestrel-e72f205a-jdk26

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