Lines Matching full:guarantees

49      - Guarantees.
224 GUARANTEES
227 There are some minimal guarantees that may be expected of a CPU:
310 And there are anti-guarantees:
312  (*) These guarantees do not apply to bitfields, because compilers often
323  (*) These guarantees apply only to properly aligned and sized scalar
330      guarantees were introduced into the C11 standard, so beware when
414      under consideration guarantees that for any load preceding it, if that
468      This acts as a one-way permeable barrier.  It guarantees that all memory
483      This also acts as a one-way permeable barrier.  It guarantees that all
516 Note that these are the _minimum_ guarantees.  Different architectures may give
517 more substantial guarantees, but they may _not_ be relied upon outside of arch
1360 instead guarantees only that a given store becomes visible at the same
1961 provide more substantial guarantees, but these may not be relied upon outside
2233 In terms of memory ordering, these functions all provide the same guarantees of
2529 guarantees:
2536 	ioremap()), the ordering guarantees are as follows:
2578 	underlying architecture and therefore the guarantees listed above cannot
2584 	ordering guarantees. Specifically, they do not guarantee ordering with
2596 	guarantees of readX_relaxed() and writeX_relaxed(), as documented above.
2606 	internal virtual memory mapping, the portable ordering guarantees
2619 	guarantees as readsX() and writesX() respectively when accessing a