8257422: [lworld] Problems with scalarized inline type return and incremental inlining

[TobiHartmann]

TestCallingConvention spuriously fails with -Xcomp and -XX:-TieredCompilation due to incremental inlining not properly handling scalarized inline type returns in rare cases. The actual fix is in parse1.cpp where we accidentally use an inline type PhiNode to return an inline type ptr when incrementally inlining (in some cases, that also manifests as crashes during compilation).

I've also refactored some related code, added stronger asserts, improved comments and added tests that reproduce the issue more reliably.

Thanks,
Tobias

---

Progress

• Change must not contain extraneous whitespace

Issue

• JDK-8257422: [lworld] Problems with scalarized inline type return and incremental inlining

Download

$ git fetch https://git.openjdk.java.net/valhalla pull/285/head:pull/285
$ git checkout pull/285

[bridgekeeper]

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

[openjdk]

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

8257422: [lworld] Problems with scalarized inline type return and incremental inlining

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 2 new commits pushed to the lworld branch:

• 1abd037: [lworld] Missed disabling testcase that does not pack well with -XX:ForceNonTearable
• 7a8c405: 8257446: [lworld] VM flag PrintInlineLayout doesn't work anymore

Please see this link for an up-to-date comparison between the source branch of this pull request and the lworld 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 lworld branch, type /integrate in a new comment.

[mlbridge]

Webrevs

• 00: Full (0c19765)

[TobiHartmann]

/integrate

[openjdk]

@TobiHartmann Since your change was applied there have been 147 commits pushed to the lworld branch:

• 8efeb68: Merge jdk
• 7aed9b6: 8256016: Dacapo24H.java failed with "assert(false) failed: unscheduable graph"
• 26e6cb3: 8256489: Make gtest for long path names on Windows more resilient in the presence of virus scanners
• 911f16d: 8257056: Submit workflow should apt-get update to avoid package installation errors
• b0bd0c2: 8256755: Update build.tools.depend.Depend to handle record components in API signatures
• 9aeadbb: 8256865: Foreign Memory Access and Linker API are missing NPE checks
• 8cd2e0f: 8243315: ParallelScavengeHeap::initialize() passes GenAlignment as page size to os::trace_page_sizes instead of actual page size
• cdb41ba: 8255904: Remove superfluous use of reflection in Class::isRecord
• c45725e: 8256747: GitHub Actions: decouple the hotspot build-only jobs from Linux x64 testing
• 79e57ac: 8256643: Terminally deprecate ThreadGroup stop, destroy, isDestroyed, setDaemon and isDaemon
• ... and 137 more: https://git.openjdk.java.net/valhalla/compare/41ee0c8da696b7dc23adec8b11bb437a58e1c8dd...lworld

Your commit was automatically rebased without conflicts.

Pushed as commit 8680152.

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