37 be moved across a volatile load freely, but not an Acquire load.
113 A ``fence`` provides Acquire and/or Release ordering which is not part of
115 A Monotonic load followed by an Acquire fence is roughly equivalent to an
116 Acquire load, and a Monotonic store following a Release fence is roughly
118 an Acquire and a Release fence, and offer some additional complicated
134 Acquire/Release. (See also `LangRef Ordering <LangRef.html#ordering>`_.)
248 Acquire  section in Atomic orderings
251 Acquire provides a barrier of the sort necessary to acquire a lock to access
260   Acquire only provides a semantic guarantee when paired with a Release
265   also possible to move stores from before an Acquire load or read-modify-write
266   operation to after it, and move non-Acquire loads from before an Acquire
271   except x86 and SPARC) require some sort of fence to maintain the Acquire
276   maintain Acquire semantics for a memory operation.
281 Release is similar to Acquire, but with a barrier of the sort necessary to
289   Release only provides a semantic guarantee when paired with a Acquire
299   See the section on Acquire; a fence before the relevant operation is usually
307 AcquireRelease (``acq_rel`` in IR) provides both an Acquire and a Release
315   Acquire only provides a semantic guarantee when paired with a Release
323   This operation has Acquire and Release semantics; see the sections on Acquire
329 SequentiallyConsistent (``seq_cst`` in IR) provides Acquire semantics for loads
345   for Acquire loads and Release stores, except that SequentiallyConsistent
349   SequentiallyConsistent loads minimally require the same barriers as Acquire
377 * Alias analysis: Note that AA will return ModRef for anything Acquire or
445 On ARM (before v8), MIPS, and many other RISC architectures, Acquire, Release,