Skip to content

8358751: C2: Recursive inlining check for compiled lambda forms is broken#2294

Closed
wkia wants to merge 2 commits intoopenjdk:masterfrom
wkia:bp8358751
Closed

8358751: C2: Recursive inlining check for compiled lambda forms is broken#2294
wkia wants to merge 2 commits intoopenjdk:masterfrom
wkia:bp8358751

Conversation

@wkia
Copy link

@wkia wkia commented Oct 3, 2025

This is backport of JDK-8358751, as it's reported jdk21 is affected.

Clean backport. Tier1 is OK.

The reproducer crashes before the fix, and OK after the fix.


Progress

  • Change must not contain extraneous whitespace
  • Commit message must refer to an issue
  • JDK-8358751 needs maintainer approval

Issue

  • JDK-8358751: C2: Recursive inlining check for compiled lambda forms is broken (Bug - P2 - Approved)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk21u-dev.git pull/2294/head:pull/2294
$ git checkout pull/2294

Update a local copy of the PR:
$ git checkout pull/2294
$ git pull https://git.openjdk.org/jdk21u-dev.git pull/2294/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 2294

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk21u-dev/pull/2294.diff

Using Webrev

Link to Webrev Comment

@bridgekeeper
Copy link

bridgekeeper bot commented Oct 3, 2025

👋 Welcome back rmarchenko! 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 Oct 3, 2025

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

8358751: C2: Recursive inlining check for compiled lambda forms is broken

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 74 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.

As you do not have Committer status in this project an existing Committer must agree to sponsor your change.

➡️ To flag this PR as ready for integration with the above commit message, type /integrate in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

@openjdk openjdk bot changed the title Backport 9cca4f7c760bea9bf79f7c03f37a70449acad51e 8358751: C2: Recursive inlining check for compiled lambda forms is broken Oct 3, 2025
@openjdk
Copy link

openjdk bot commented Oct 3, 2025

This backport pull request has now been updated with issue from the original commit.

@openjdk openjdk bot added backport Port of a pull request already in a different code base clean Identical backport; no merge resolution required labels Oct 3, 2025
@openjdk
Copy link

openjdk bot commented Oct 3, 2025

⚠️ @wkia This change is now ready for you to apply for maintainer approval. This can be done directly in each associated issue or by using the /approval command.

@openjdk openjdk bot added the rfr Pull request is ready for review label Oct 3, 2025
@mlbridge
Copy link

mlbridge bot commented Oct 3, 2025

Webrevs

@wkia
Copy link
Author

wkia commented Oct 3, 2025

/approval request I'd like to backport this to jdk21u-dev, as it's reported jdk21 is affected. Clean backport. Tier1 is OK. The reproducer crashes before the fix, and OK after the fix.

@openjdk
Copy link

openjdk bot commented Oct 3, 2025

@wkia
8358751: The approval request has been created successfully.

@openjdk openjdk bot added the approval Requires approval; will be removed when approval is received label Oct 3, 2025
@GoeLin
Copy link
Member

GoeLin commented Oct 4, 2025

Please backport to 25 first. Removing label in meantime.

@openjdk openjdk bot removed the approval Requires approval; will be removed when approval is received label Oct 4, 2025
@openjdk openjdk bot added the approval Requires approval; will be removed when approval is received label Oct 14, 2025
@GoeLin
Copy link
Member

GoeLin commented Oct 17, 2025

Hi @wkia
this fix is brand new and in a central component.
I would prefer to delay this to the next release of 21.
Do you know which change caused this issue?
Could you please link it to the JBS issue?
Thanks.

@wkia
Copy link
Author

wkia commented Oct 17, 2025

@GoeLin Probably it's caused by "8011138: C2: stack overflow in compiler thread because of recursive inlining of lambda form methods".
This issue is mentioned in JDK-8358751's comments, but I don't know why it's not linked.

@GoeLin
Copy link
Member

GoeLin commented Oct 20, 2025

Ah, 8011138 is not visible to the public, so we an not link it.
Let's wait for April, please.

@bridgekeeper
Copy link

bridgekeeper bot commented Nov 17, 2025

@wkia This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply issue a /touch or /keepalive command to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration!

@bridgekeeper
Copy link

bridgekeeper bot commented Dec 15, 2025

@wkia This pull request has been inactive for more than 8 weeks and will now be automatically closed. If you would like to continue working on this pull request in the future, feel free to reopen it! This can be done using the /open pull request command.

@bridgekeeper bridgekeeper bot closed this Dec 15, 2025
@wkia
Copy link
Author

wkia commented Dec 15, 2025

/open

@openjdk openjdk bot reopened this Dec 15, 2025
@openjdk
Copy link

openjdk bot commented Dec 15, 2025

@wkia This pull request is now open

@GoeLin
Copy link
Member

GoeLin commented Dec 17, 2025

HI @wkia
Can you please merge head and rerun the GHA tests?

@wkia
Copy link
Author

wkia commented Dec 19, 2025

Hi @GoeLin
Done

@openjdk openjdk bot added ready Pull request is ready to be integrated and removed approval Requires approval; will be removed when approval is received labels Jan 5, 2026
@wkia
Copy link
Author

wkia commented Jan 5, 2026

/integrate

@openjdk openjdk bot added the sponsor Pull request is ready to be sponsored label Jan 5, 2026
@openjdk
Copy link

openjdk bot commented Jan 5, 2026

@wkia
Your change (at version e32908a) is now ready to be sponsored by a Committer.

@bridgekeeper
Copy link

bridgekeeper bot commented Feb 2, 2026

@wkia This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply issue a /touch or /keepalive command to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration!

@wkia
Copy link
Author

wkia commented Feb 2, 2026

/touch

@openjdk
Copy link

openjdk bot commented Feb 2, 2026

@wkia The pull request is being re-evaluated and the inactivity timeout has been reset.

@GoeLin
Copy link
Member

GoeLin commented Feb 11, 2026

/sponsor

@openjdk
Copy link

openjdk bot commented Feb 11, 2026

Going to push as commit 749aaf6.
Since your change was applied there have been 79 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 Feb 11, 2026
@openjdk openjdk bot closed this Feb 11, 2026
@openjdk openjdk bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review sponsor Pull request is ready to be sponsored labels Feb 11, 2026
@openjdk
Copy link

openjdk bot commented Feb 11, 2026

@GoeLin @wkia Pushed as commit 749aaf6.

💡 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

backport Port of a pull request already in a different code base clean Identical backport; no merge resolution required integrated Pull request has been integrated

Development

Successfully merging this pull request may close these issues.

2 participants