Change:
/// /// This ordering is only applicable for operations that can perform a load. /// <del> /// Corresponds to LLVM's [`Acquire`] ordering. </del> <ins> /// Corresponds to [`memory_order_acquire`] in C++20. </ins> /// <del> /// [`Acquire`]: https://llvm.org/docs/Atomics.html#acquire /// [`Release`]: https://llvm.org/docs/Atomics.html#release /// [`Relaxed`]: https://llvm.org/docs/Atomics.html#monotonic </del> <ins> /// [`Acquire`]: #variant.Acquire /// [`Release`]: #variant.Release /// [`Relaxed`]: #variant.Relaxed /// [`memory_order_acquire`]: https://en.cppreference.com/w/cpp/atomic/memory_order#Release-Acquire_ordering </ins> #[stable(feature = "rust1", since = "1.0.0")] Acquire, /// Has the effects of both [`Acquire`] and [`Release`] together:

Discussion:
that our docs say That's not really correct though... at least according to the Nomicon, we , which is different from LLVM's. The kinds of ordering that exist are the same (at least insofar as Rust exposes them), but the details of the rules around data races are different. Code that mixes atomic and non-atomic accesses on the same location can behave differently under both models (concretely, some programs that are UB under C11 are no longer UB under LLVM). So if people interpret "same as LLVM's" too strongly, they might be mislead. Cc
I think this question is actually trickier than it sounds, because I see periodical interest in bringing in some of LLVM's extensions with respect to C11 (, element-wise atomic memcpy...) to Rust. A clear "we use the C11 memory model, not LLVM's" stance could be interpreted as closing that door.
Well as far as I am concerned that is the current stance. But it doesn't close any doors. Switching from C11 to LLVM's model makes strictly more programs defined, that's the only difference. IOW, that's a non-breaking change. Moving from LLVM's to C's model, on the other hand, turns some well-defined programs into UB. So, C11 is also the conservative future-compatible choice here.
This is not true of all of LLVM's features though. For example, LLVM's unordered atomics can be emulated with relaxed C11 atomics without loss of correctness (but potentially at a performance cost). In this respect, there is room for a "we mostly follow the C11 model, but allow ourselves to adopt LLVM extensions which can be pessimistically implemented on top of the C11 building blocks" stance.
is not a thing in Rust right now though. :) So for the APIs we currently expose, saying we use C11 is the conservative future-compatible choice -- and I actually think this is the current normative choice, based on what the Nomicon says (it's also what I told everyone over the last years). Extending Rust's API beyond C11's would change that game -- I'll comment on when I find the time. But I don't see any reason why that would be in conflict with saying that right now, Rust follows C11.

Point taken ;)
Oh and I don't think element-wise atomic memcpy is even an extension of the model; that's just an intrinsic for a loop that can already be expressed in the existing model.
Well, today LLVM is clearly unable to optimize a loop of the corresponding relaxed atomic load/store operation into a performant implementation of its element-wise memcpy intrinsic, because it is unable to coalesce neighboring atomic loads and stores. But that's arguably an LLVM optimizer issue, not a semantic limitation of C11 atomics.
Indeed that would have been my argument. :)
Seems like the standard library should be fixed. Want to file a PR?
PR filed: