How strongly an atomic access or a barrier is ordered against everything around it.
The C11 memory model’s orderings, which gcc’s __atomic_ family took from the same place. This
is spelled here rather than reused from the IR because nothing in this crate knows what an IR
is, and the walk that builds one is where the two are put side by side.
memory_order_consume is not here. Every compiler in use today gives it the same code as
acquire, C++17 discourages it, and a spelling of it that means acquire would be a name whose
only effect is to make a reader think something was implemented. The number the source wrote is
read and turned into Ordering::Acquire where it appears, and the fact that it was written is
not carried any further.