Lines Matching refs:as

8 meant as a guide to best practices, and warns against a variety of possible
13 as this document builds on it, and explains the liberties XNU takes with said
28 by C11 as relaxed, consume, acquire, release, acq\_rel and seq\_cst.
59 does with other plain memory accesess such as coalescing, reordering, hoisting
103    as if their type was `_Atomic volatile` qualified.
107    where the name is the same as in C11 without the `memory_order_` prefix,
167 that involve more costly codegen (such as compare exchange loops).
239 for the failure case ordering, as it is what is used most of the time.
242 as `os_atomic_rmw_loop` offers a much better alternative for CAS-loops.
293 as these may cause the store-conditional to always fail.
327 most compilers, clang included, implement it as an equivalent
335 implicit compiler barrier, that can be used as a root for a chain of hardware
370          * This isn't safe, as there's absolutely no hardware dependency involved.
417 provides a similar construct as a language feature instead.