8311964: Some jtreg tests failing on x86 with error 'unrecognized VM options' (C2 flags)

[sendaoYan]

Hi,

Clean backport of JDK-8311964. Backport has been verified as bellow. Only change the testcases, the risk is low.

There 3 testcases run complaint "Unrecognized VM option" with linux-x86-client-release jdk before this PR. LoopUnswitching, OptimizeFill and StressCCP are all C2 flags.
test command:

rm -rf tmp/ ; jtreg -v:fail,error -nr -w tmp -jdk:build/linux-x86-client-release/images/jdk/ test/hotspot/jtreg/compiler/loopopts/TestBackedgeLoadArrayFillMain.java test/hotspot/jtreg/compiler/loopopts/TestInfiniteLoopWithUnmergedBackedgesMain.java test/hotspot/jtreg/compiler/rangechecks/TestRangeCheckCmpUOverflowVsSub.java 2>&1 | grep "Unrecognized VM option"

After this PR, there 3 testcases won't be selected when the test jdk is linux-x86-client.

Thanks,
-sendao

---

Progress

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

Issue

• JDK-8311964: Some jtreg tests failing on x86 with error 'unrecognized VM options' (C2 flags) (Bug - P4 - Approved)

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 279

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

Using diff file

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

Webrev

Link to Webrev Comment

[bridgekeeper]

👋 Welcome back syan! 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 from the original commit.

[openjdk]

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

[sendaoYan]

/approval JDK-8311964 request

[openjdk]

@sendaoYan
JDK-8311964: The approval request has been created successfully.

[mlbridge]

Webrevs

• 01: Full - Incremental (02c1674e)
• 00: Full (93cbcc4f)

[GoeLin]

Hi @sendaoYan
Same as with your orther request. The comment is missing. Please read https://wiki.openjdk.org/display/JDKUpdates/How+to+contribute+or+backport+a+fix
I won't check and comment all of your backports, instead I will remove the tag of all the ones I find today. Please double check all of them, you find a list here: https://github.com/pulls if you are logged in to github.

[sendaoYan]

Hi @sendaoYan Same as with your orther request. The comment is missing. Please read https://wiki.openjdk.org/display/JDKUpdates/How+to+contribute+or+backport+a+fix I won't check and comment all of your backports, instead I will remove the tag of all the ones I find today. Please double check all of them, you find a list here: https://github.com/pulls if you are logged in to github.

Thanks, I will check all mine PR there few days.

[openjdk]

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

8311964: Some jtreg tests failing on x86 with error 'unrecognized VM options' (C2 flags)

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 no new commits pushed to the master branch. If another commit should be pushed before you perform the /integrate command, your PR will be automatically rebased. If you prefer to avoid any potential 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).

[bridgekeeper]

@sendaoYan This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration!

[sendaoYan]

/approval JDK-8311964 request "Clean backport. Backport has been verified. Only change the testcases, the risk is low."

[openjdk]

@sendaoYan
JDK-8311964: The approval request has been updated successfully.

[bridgekeeper]

@sendaoYan This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration!

[sendaoYan]

/integrate

[openjdk]

@sendaoYan
Your change (at version 93cbcc4) is now ready to be sponsored by a Committer.

[shipilev]

I think is PR base is too old, bot says there are 318 commits ahead of it. Can you please merge from master to see if it still works?

[sendaoYan]

I think is PR base is too old, bot says there are 318 commits ahead of it. Can you please merge from master to see if it still works?

I have merged from master just now. Thanks for the advice.

[sendaoYan]

/integrate

[openjdk]

@sendaoYan
Your change (at version 02c1674) is now ready to be sponsored by a Committer.

[TheRealMDoerr]

/sponsor

[openjdk]

Going to push as commit fbb0f4c.
Since your change was applied there has been 1 commit pushed to the master branch:

• bddd6a7: 8321925: sun/security/mscapi/KeytoolChangeAlias.java fails with "Alias <246810> does not exist"

Your commit was automatically rebased without conflicts.

[openjdk]

@TheRealMDoerr @sendaoYan Pushed as commit fbb0f4c.

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

[sendaoYan]

/sponsor

Thanks.