Skip to content

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 - Requested)

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

❗ This change is not yet ready to be integrated.
See the Progress checklist in the description for automated requirements.

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

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

Labels

approval Requires approval; will be removed when approval is received backport Port of a pull request already in a different code base clean Identical backport; no merge resolution required rfr Pull request is ready for review

Development

Successfully merging this pull request may close these issues.

2 participants