Lines Matching full:atomic

39 .Nd atomic operations
81 Atomic operations are commonly used to implement reference counts and as
93 inherently atomic if the integer is naturally aligned and its size does not
96 the compiler, whereas atomic operations are always performed.
98 When atomic operations are performed on cache-coherent memory, all
101 When an atomic load is performed on a location in cache-coherent memory,
102 it reads the entire value that was defined by the last atomic store to
104 An atomic load will never return a value out of thin air.
105 When an atomic store is performed on a location, no other thread or
111 identical to the semantics of similarly named C11 atomic operations.
113 Most atomic operations act upon a specific
116 In contrast to C11 atomic operations,
118 atomic operations are performed on ordinary integer types.
170 on a thread's accesses, a programmer can use atomic operations with
176 Atomic operations on memory have up to three variants.
185 An atomic operation can only have
189 When an atomic operation has acquire semantics, a load performed as
194 completed before a load from the atomic operation is performed.
205 An atomic operation can only have
208 When an atomic operation has release semantics, all prior loads or stores
211 Conversely, release semantics do not require that a store from the atomic
234 In effect, atomic operations with acquire and release semantics establish
251 that of the atomic operation can be reordered in relation to the
252 atomic operation.
267 before the atomic, might be observed as executed after the load
268 that is the part of the atomic operation (but not after the store
270 Similarly, accesses after the atomic might be observed as executed
273 Alternatively, a programmer can use atomic thread fence operations to
275 In contrast to other atomic operations, fences do not, themselves, access
306 another thread when an atomic load that is prior to the acquire fence (by
307 program order) reads the value written by an atomic store that is subsequent
318 Since neither a compiler nor a processor can foresee which (atomic) load
319 will read the value written by an (atomic) store, the ordering constraints
338 In multiprocessor systems, the atomicity of the atomic operations on memory
528 is currently not implemented for some of the atomic operations on the