Lines Matching full:guarantees

49      - Guarantees.
223 GUARANTEES
226 There are some minimal guarantees that may be expected of a CPU:
309 And there are anti-guarantees:
311  (*) These guarantees do not apply to bitfields, because compilers often
322  (*) These guarantees apply only to properly aligned and sized scalar
329      guarantees were introduced into the C11 standard, so beware when
418      the CPU under consideration guarantees that for any load preceding it,
476      This acts as a one-way permeable barrier.  It guarantees that all memory
491      This also acts as a one-way permeable barrier.  It guarantees that all
524 Note that these are the _minimum_ guarantees.  Different architectures may give
525 more substantial guarantees, but they may _not_ be relied upon outside of arch
1379 instead guarantees only that a given store becomes visible at the same
1954      Note that the dma_*() barriers do not provide any ordering guarantees for
1989 provide more substantial guarantees, but these may not be relied upon outside
2261 In terms of memory ordering, these functions all provide the same guarantees of
2557 guarantees:
2564 	ioremap()), the ordering guarantees are as follows:
2606 	underlying architecture and therefore the guarantees listed above cannot
2612 	ordering guarantees. Specifically, they do not guarantee ordering with
2624 	guarantees of readX_relaxed() and writeX_relaxed(), as documented above.
2634 	internal virtual memory mapping, the portable ordering guarantees
2647 	guarantees as readsX() and writesX() respectively when accessing a