Add storeStoreFence Opcode for storeStoreFence intrinsic #19298
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.
This commit adds the
storeStoreFence opcode
to represent StoreStore barrier semantics for Java. This barrier is provided as a Java class library@IntrinsicCandidate
withUnsafe.storeStoreFence()
. Code generation functionality is added for each backend where appropriate.StoreStore barriers in Java prevent the reordering of store operations before and after the barrier. Currently, this barrier is implemented through the storeFence opcode, which provides additional but unneeded reordering guarantees.
The following extensions have been added for each backend which currently handles the storeFence opcode.
storeStoreFence
is implemented as anop
storeStoreFence
is implemented asdmb ishst
see (Investigate best AArch64 instructions for memory fences #6332)storeStoreFence
is implemented with alwsync
storeFence
is unused, sostoreStoreFence
is unimplemented.Depends on: eclipse/omr#7310