Lines Matching refs:an

42 - an *explicit* variant where memory orderings can be specified,
46 When an `_Atomic` qualified variable is accessed directly without using
149 with an optional barrier ordering. It is implemented with C11's
173 - `inc`: atomic increment (equivalent to an atomic add of `1`),
174 - `dec`: atomic decrement (equivalent to an atomic sub of `1`),
230    which has an extra `orig_value` argument which must be a pointer to a local
296 Use of `continue` within an `os_atomic_rmw_loop` is also invalid, instead an
297 `os_atomic_rmw_loop_give_up(goto again)` jumping to an `again:` label placed
327 most compilers, clang included, implement it as an equivalent
331 As an attempt to provide a replacement for this, `<os/atomic_private.h>`
332 implements an entirely new *dependency* memory ordering.
334 The purpose of this ordering is to provide a relaxed load followed by an
350 Here is an example of how it is meant to be used:
371          * Using an acquire barrier would of course fix it but is quite expensive...
406 3. `os_atomic_load_with_dependency_on` to do an otherwise related relaxed load
409 4. `os_atomic_make_dependency` to create an opaque token out of a given