8342496: C2/Shenandoah: SEGV in compiled code when running jcstress

[RadekCap]

Backport of JDK-8342496 - C2/Shenandoah: SEGV in compiled code when running jcstress

Clean backport.
Passed tier 1 tests.
Passed gtests.

---

Progress

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

Issue

• JDK-8342496: C2/Shenandoah: SEGV in compiled code when running jcstress (Bug - P3)

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 2995

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

Using diff file

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

Using Webrev

Link to Webrev Comment

[bridgekeeper]

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

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

[openjdk]

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

[openjdk]

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

[mlbridge]

Webrevs

• 00: Full (afddced2)

[jerboaa]

@RadekCap Did you run the test without the patch an with it? If so what were the results?

[RadekCap]

No, because in the bug 11is listed as an affected version.

[RadekCap]

("It's fixing the java/lang/invoke/PrivateInvokeTest.java#PrivateInvokeTest failure." has been removed from the first comment as it was relict from the template which shouldn't be there.)

[jerboaa]

No, because in the bug 11is listed as an affected version.

Please do so. In fact, it's the least one should do to sanity-check a patch. I'm not sure whether this test has been run on JDK 11. Thanks!