opal_atomic_rmb: GCC has fixed its acquire fence barrier in its 8 release [v5.0.x] #10128
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bwbarrett
approved these changes
Mar 16, 2022
…ease Only force a full memory barrier for GCC releases prior to 8.1.0. Signed-off-by: Joseph Schuchart <schuchart@icl.utk.edu> (cherry picked from commit 935ee76)
devreal
force-pushed
the
atomic_acq_fence_fix_v5.0.x
branch
from
2fc19b3 to
ad139e8
Compare
|
bot:ibm:retest |
|
bot:aws:retest |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Only force a full memory barrier for GCC releases prior to 8.1.0.
Backport of #10118 to v5.0.x
Signed-off-by: Joseph Schuchart schuchart@icl.utk.edu