A cross-thread sequentially consistent fence should be lowered into z/Architecture's BCR serialization instruction, instead of causing a fatal error in the back-end.
Details
Details
Diff Detail
Diff Detail
Event Timeline
Comment Actions
This seems overly conservative: I think we only need a BCR serialization instruction for sequentially-consistent cross-thread fences. For everything else, a pure compiler barrier should be sufficient. See e.g. the X86 back-end for how to implement that check.
Comment Actions
I have updated the patch to mimic the behaviour of ATOMIC_FENCE on X86, as suggested.