8357793: [PPC64] VM crashes with -XX:-UseSIGTRAP -XX:-ImplicitNullChecks

[TheRealMDoerr]

Backport of JDK-8357793. Version from jdk21u-dev applies cleanly, but InterpreterMacroAssembler::load_klass_check_null_throw didn't exist in 17u. I've taken the PPC64 interpreter parts from openjdk/jdk@7cf7e0a.

Testing:
make run-test TEST=hotspot:tier1 JTREG="VM_OPTIONS=-XX:-UseSIGTRAP -XX:-ImplicitNullChecks" has passed.

---

Progress

• Change must be properly reviewed (1 review required, with at least 1 Reviewer)
• Change must not contain extraneous whitespace
• JDK-8357793 needs maintainer approval
• Commit message must refer to an issue

Issue

• JDK-8357793: [PPC64] VM crashes with -XX:-UseSIGTRAP -XX:-ImplicitNullChecks (Bug - P3 - Approved)

Reviewers

• Matthias Baesken (@MBaesken - Reviewer)

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 3619

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

Using diff file

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

Using Webrev

Link to Webrev Comment

[bridgekeeper]

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

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

8357793: [PPC64] VM crashes with -XX:-UseSIGTRAP -XX:-ImplicitNullChecks

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

• 95fe05a: 8136895: Writer not closed with disk full error, file resource leaked
• f7492dd: 8312475: org.jline.util.PumpReader signed byte problem
• 4241313: 8354941: Build failure with glibc 2.42 due to uabs() name collision
• ... and 11 more: https://git.openjdk.org/jdk17u-dev/compare/3a46af4ac3ba8d330a7fb6f0858113cca6e3d9a2...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]

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

[mlbridge]

Webrevs

• 00: Full (b3cabf04)

[openjdk]

⚠️ @TheRealMDoerr 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.

[TheRealMDoerr]

/approval request JDK17 is affected by this bug. Backport reason and risk are the same as in the jdk21u-fix-request. The version from 21u applies cleanly, but required a trivial addition which has been reviewed.

[openjdk]

@TheRealMDoerr
8357793: The approval request has been created successfully.

[TheRealMDoerr]

/integrate

[openjdk]

Going to push as commit 3ee1839.
Since your change was applied there have been 14 commits pushed to the master branch:

• 95fe05a: 8136895: Writer not closed with disk full error, file resource leaked
• f7492dd: 8312475: org.jline.util.PumpReader signed byte problem
• 4241313: 8354941: Build failure with glibc 2.42 due to uabs() name collision
• ... and 11 more: https://git.openjdk.org/jdk17u-dev/compare/3a46af4ac3ba8d330a7fb6f0858113cca6e3d9a2...master

Your commit was automatically rebased without conflicts.

[openjdk]

@TheRealMDoerr Pushed as commit 3ee1839.

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