arch/riscv64.sh: Disable emitting fence.tso on GCC 15+ #71
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.
GCC 15 introduces a new compiler flag,
-m{,no-}fence-tso, to control the usage offence.tsoinstruction (which is not supported on some old T-Head cores, such as the ones used on TH1520/SG2042). When it's disabled, more strongfence rw,rwis emitted and correctness is then not affected.Disable emitting this instruction now, because all buildbots of riscv64 are currently SG2042, and no CPU cores are known to benefit from
fence.tsoyet.==================
cc @RevySR