-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
8330242: RISC-V: Simplify and remove CORRECT_COMPILER_ATOMIC_SUPPORT in atomic_linux_riscv.hpp #18780
Conversation
…in atomic_linux_riscv.hpp
👋 Welcome back gcao! A progress list of the required criteria for merging this PR into |
@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:
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 34 new commits pushed to the
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. Possible candidates are the reviewers of this PR (@RealFYang, @robehn) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks fine to me. Thanks for the cleanup.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
@RealFYang @robehn : Thanks for the review. |
/sponsor |
Going to push as commit cd4c3aa.
Your commit was automatically rebased without conflicts. |
@RealFYang @zifeihan Pushed as commit cd4c3aa. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
/backport jdk22u |
@zifeihan the backport was successfully created on the branch backport-zifeihan-cd4c3aac in my personal fork of openjdk/jdk22u. To create a pull request with this backport targeting openjdk/jdk22u:master, just click the following link: The title of the pull request is automatically filled in correctly and below you find a suggestion for the pull request body:
If you need to update the source branch of the pull then run the following commands in a local clone of your personal fork of openjdk/jdk22u:
|
Previously, we fixed JDK-8326936 with a workaround for one GCC bug [1]. We define a new
CORRECT_COMPILER_ATOMIC_SUPPORT
macro when building with GCC >= 14. Now this bug has been fixed in gcc trunk and has been backported to GCC-13 branch. The__atomic_compare_exchange
atomic operation will be usable for the next GCC-13.3 release. So we should relax the condition and require GCC > 13.2. This will also help removeCORRECT_COMPILER_ATOMIC_SUPPORT
macro and reuse a singleFULL_COMPILER_ATOMIC_SUPPORT
macro.[1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114130
Testing
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/18780/head:pull/18780
$ git checkout pull/18780
Update a local copy of the PR:
$ git checkout pull/18780
$ git pull https://git.openjdk.org/jdk.git pull/18780/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 18780
View PR using the GUI difftool:
$ git pr show -t 18780
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/18780.diff
Webrev
Link to Webrev Comment