8330242: RISC-V: Simplify and remove CORRECT_COMPILER_ATOMIC_SUPPORT in atomic_linux_riscv.hpp

[zifeihan]

This is a followup fix for JDK-8326936 which has been backported to jdk22u. I would like to also have this for jdk22u so that gcc __atomic_compare_exchange atomic operation could still be used for the upcoming gcc-13.3 release. This is a risc-v specific change. Backport is clean, risk is low.

Testing

• The affected jtreg test cases all pass with jdk release built with latest gcc-13 development branch.

---

Progress

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

Issue

• JDK-8330242: RISC-V: Simplify and remove CORRECT_COMPILER_ATOMIC_SUPPORT in atomic_linux_riscv.hpp (Enhancement - P4 - Approved)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk22u.git pull/146/head:pull/146
$ git checkout pull/146

Update a local copy of the PR:
$ git checkout pull/146
$ git pull https://git.openjdk.org/jdk22u.git pull/146/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 146

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk22u/pull/146.diff

Webrev

Link to Webrev Comment

[bridgekeeper]

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

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

8330242: RISC-V: Simplify and remove CORRECT_COMPILER_ATOMIC_SUPPORT in atomic_linux_riscv.hpp

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

• 829d047: Merge
• 8ba20c7: 8327391: Add SipHash attribution file
• e351052: 8325313: Header format error in TestIntrinsicBailOut after JDK-8317299
• 1d7689d: Merge
• ae46fb7: Merge
• bf87bb7: Merge
• 733b837: 8322122: Enhance generation of addresses
• a7ac67c: Merge
• 0082d4c: Merge
• 8ac813a: 8315708: Enhance HTTP/2 client usage
• ... and 8 more: https://git.openjdk.org/jdk22u/compare/c45dbbcf20f5febf330bdbfc21260697aa01c0a2...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.

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).

[openjdk]

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

[mlbridge]

Webrevs

• 00: Full (96aa4ec8)

[zifeihan]

/integrate

[openjdk]

@zifeihan
Your change (at version 96aa4ec) is now ready to be sponsored by a Committer.

[RealFYang]

/sponsor

[openjdk]

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

• 829d047: Merge
• 8ba20c7: 8327391: Add SipHash attribution file
• e351052: 8325313: Header format error in TestIntrinsicBailOut after JDK-8317299
• 1d7689d: Merge
• ae46fb7: Merge
• bf87bb7: Merge
• 733b837: 8322122: Enhance generation of addresses
• a7ac67c: Merge
• 0082d4c: Merge
• 8ac813a: 8315708: Enhance HTTP/2 client usage
• ... and 8 more: https://git.openjdk.org/jdk22u/compare/c45dbbcf20f5febf330bdbfc21260697aa01c0a2...master

Your commit was automatically rebased without conflicts.

[openjdk]

@RealFYang @zifeihan Pushed as commit 2ae0188.

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