8378149: [s390] Non-C2 / minimal JVM crashes in the build

[offamitkumar]

This build failure will only occur if continuations support is enabled. In my continuation port when I did the build it failed with the same error which we have seen in past on ppc platform.

Testing: Build fixed with the current code change and on headstream I didn't see any new issue appearing for s390 with tier1 testcase run.

CC: @MBaesken @TheRealMDoerr will it be possible if you take a look at this PR as changes are similar to #23794 . Let me know if there is requirement to ran other test with any different vm.

---

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-8378149: [s390] Non-C2 / minimal JVM crashes in the build (Bug - P4)

Reviewers

• Martin Doerr (@TheRealMDoerr - Reviewer)
• Matthias Baesken (@MBaesken - Reviewer)

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 29777

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

Using diff file

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

Using Webrev

Link to Webrev Comment

[bridgekeeper]

👋 Welcome back amitkumar! 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]

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

8378149: [s390] Non-C2 / minimal JVM crashes in the build

Reviewed-by: mdoerr, mbaesken

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

• d02ac57: 8377983: (zipfs) ZipFileSystem.initCEN needlessly reads END header
• a86a847: 8378076: Improve inlining around oop_oop_iterate
• 27ed9a8: 8378098: Problem list compiler/vectorization/TestVectorAlgorithms.java with# on AIX and Linux s390x
• ... and 2 more: https://git.openjdk.org/jdk/compare/bfac97c5c14b188dda662d1f9591bdc22034161c...master

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]

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

[mlbridge]

Webrevs

• 00: Full (85d2d44e)

[MBaesken]

Let me know if there is requirement to ran other test with any different vm.

I think what you tested sounds sufficient.

[TheRealMDoerr]

LGTM.

[offamitkumar]

Thanks for approval :) , failure on windows-x64 is unrelated to this PR's changes.

/integrate

[openjdk]

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

• c594da7: 8326487: ZipFileSystem.getPath("").getFileName() returns null instead of an empty Path
• c8338be: 8376534: Source launcher instantiates wrong class on inherited instance main
• a20a1ac: 8378119: GenShen: Restore log message about characteristics of promotion efforts
• ... and 6 more: https://git.openjdk.org/jdk/compare/bfac97c5c14b188dda662d1f9591bdc22034161c...master

Your commit was automatically rebased without conflicts.

[openjdk]

@offamitkumar Pushed as commit 7d2b6ed.

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