shac ron ₪‎ on Nostr: It is a compiler fence, which is what people actually mean when they use volatile. ...

It is a compiler fence, which is what people actually mean when they use volatile. Yes it restricts ordering somewhat in the code gen, but ultimately generates a plain load or store instruction.

On any sane architecture, atomic basic types are going to be aligned such that tearing is a non-issue. For types are bigger than the size your core can load or store atomically, I believe the only option is to cast away the _Atomic