Lines Matching full:operation
113 memory operation can happen on any thread between the load and store. Note that
117 another operation; it is normally used along with Monotonic memory operations.
181 guarantees the operation to be lock-free, so it do not depend on the data being
184 you need such an operation, use explicit locking.
246 to appear as a single operation.
261 operation.
266 operation to after it, and move non-Acquire loads from before an Acquire
267 operation to after it.
275 such a fence after the equivalent Monotonic operation is sufficient to
276 maintain Acquire semantics for a memory operation.
290 operation.
295 operation to before it, and move non-Release stores from after an Release
296 operation to before it.
299 See the section on Acquire; a fence before the relevant operation is usually
316 operation, and vice versa.
323 This operation has Acquire and Release semantics; see the sections on Acquire
366 operation.
369 that they return true for any operation which is volatile or at least
373 Release, and for the address accessed by any Monotonic operation.
378 it doesn't replace an atomic load or store with a non-atomic operation.
383 * ``memcpyopt``: An atomic operation cannot be optimized into part of a
411 lock-free ``cmpxchg``; such an operation can be used to implement all the other
415 error when given an operation which cannot be implemented. (The LLVM code
435 operation. Loads and stores generate normal instructions. ``cmpxchg`` and
