8239422: [TESTBUG] compiler/c1/TestPrintIRDuringConstruction.java failed when C1 is disabled

[theaoqi]

The patch applies clean. Low risk, only test changes. The modified test passed on linux-x64 with and without compiler1 (without c1: no tests selected).

---

Progress

• Change must not contain extraneous whitespace
• Commit message must refer to an issue

Issue

• JDK-8239422: [TESTBUG] compiler/c1/TestPrintIRDuringConstruction.java failed when C1 is disabled

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk11u-dev pull/544/head:pull/544
$ git checkout pull/544

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 544

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.java.net/jdk11u-dev/pull/544.diff

[bridgekeeper]

👋 Welcome back aoqi! 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 backport pull request has now been updated with issue and summary from the original commit.

[openjdk]

@theaoqi This change now passes all automated pre-integration checks.

After integration, the commit message for the final commit will be:

8239422: [TESTBUG] compiler/c1/TestPrintIRDuringConstruction.java failed when C1 is disabled

Skip test if C1 is not available.

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 1 new commit pushed to the master branch:

• 1297c26: 8275051: Shenandoah: Correct ordering of requested gc cause and gc request flag

Please see this link for an up-to-date comparison between the source branch of this pull request and the master 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.

As you do not have Committer status in this project an existing Committer must agree to sponsor your change.

➡️ To flag this PR as ready for integration with the above commit message, type /integrate in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

[mlbridge]

Webrevs

• 00: Full (2d01bc7e)

[theaoqi]

Got the jdk11u-fix-yes.

/integrate

[openjdk]

@theaoqi
Your change (at version 2d01bc7) is now ready to be sponsored by a Committer.

[RealCLanger]

/sponsor

[openjdk]

Going to push as commit 25c33bc.
Since your change was applied there have been 2 commits pushed to the master branch:

• 00255bd: 8263068: Rename safefetch.hpp to safefetch.inline.hpp
• 1297c26: 8275051: Shenandoah: Correct ordering of requested gc cause and gc request flag

Your commit was automatically rebased without conflicts.

[openjdk]

@RealCLanger @theaoqi Pushed as commit 25c33bc.

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