Lines Matching full:ordering

2 memory-ordering lives simple, as is necessary for those whose domain
3 is complex.  After all, there are bugs other than memory-ordering bugs,
4 and the time spent gaining memory-ordering knowledge is not available
139 memory ordering.
175 2.	Operations that did not return a value and provided no ordering,
178 3.	Operations that returned a value and provided full ordering, such as
180 	value-returning operations provide full ordering only conditionally.
181 	For example, cmpxchg() provides ordering only upon success.
184 provide full ordering.  These are flagged with either a _relaxed()
185 suffix (providing no ordering), or an _acquire() or _release() suffix
186 (providing limited ordering).
213 hence they do not provide any ordering guarantees at all.
225 no ordering, but they do prevent the compiler from carrying out a number
234 too easy to assume ordering, and this assumption must be avoided when
270 recipes-pairs.txt file to peel off the next layer of the memory-ordering