8252990: Intrinsify Unsafe.storeStoreFence

[shipilev]

Clean backport to improve non-x86 platforms performance.

Additional testing:

• Linux x86_64 fastdebug tier1
• Linux x86_64 fastdebug tier2
• Linux x86_64 fastdebug tier3
• Linux AArch64 fastdebug tier1
• Linux AArch64 fastdebug tier2
• Linux AArch64 fastdebug tier3

---

Progress

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

Issue

• JDK-8252990: Intrinsify Unsafe.storeStoreFence

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 1290

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

Using diff file

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

Webrev

Link to Webrev Comment

[bridgekeeper]

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

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

8252990: Intrinsify Unsafe.storeStoreFence

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.

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

[mlbridge]

Webrevs

• 01: Full - Incremental (ff2de280)
• 00: Full (40765df9)

[GoeLin]

What is wrong with the Pre-submit tests?

I'll run it through SAP nightly testing.

[shipilev]

What is wrong with the Pre-submit tests?
I'll run it through SAP nightly testing.

Missing ebde2fb, apparently. I merged from master, let's see if that helps.

[shipilev]

What is wrong with the Pre-submit tests?
I'll run it through SAP nightly testing.

Missing ebde2fb, apparently. I merged from master, let's see if that helps.

Yup, GHAs look better now. @GoeLin, please see the pending request for approval :)

[shipilev]

The testing is clean. The push approval is there.

/integrate

[openjdk]

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

• 24e91c1: 8302594: use-after-free in Node::destruct
• d964229: 8302172: [JVMCI] HotSpotResolvedJavaMethodImpl.canBeInlined must respect ForceInline
• 3e0e4f0: 8301338: Identical branch conditions in CompileBroker::print_heapinfo
• ee63f83: 8296412: Special case infinite loops with unmerged backedges in IdealLoopTree::check_safepts
• 1dee04a: 8278146: G1: Rework VM_G1Concurrent VMOp to clearly identify it as pause
• a000b2d: 8238274: (sctp) JDK-7118373 is not fixed for SctpChannel
• f969f81: 8301998: Update HarfBuzz to 7.0.1

Your commit was automatically rebased without conflicts.

[openjdk]

@shipilev Pushed as commit e6e6bed.

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