File changed.
Preview size limit exceeded, changes collapsed.
Loading
Volatile operations are explicitly specified as not synchronizing... > This is not Java’s “volatile” and has no cross-thread synchronization behavior. ... and LLVM does not model them as being synchronizing anywhere, except the definition of this attribute, which is largely unused outside the Attributor. The ordering requirements of volatile operations are already fully encoded in their memory effects (unlike what is the case for stronger-than-monotonic atomics). Clarify that "nosync" is specifically in the sense of "synchronizes-with" (rather than just any cross-thread communication) and remove volatile operations from the definition.
File changed.
Preview size limit exceeded, changes collapsed.