Lines Matching refs:compiler
10 to instruct the compiler and the CPU to restrict the order to something
26 - compiler barriers: ``barrier()``;
47 ``barrier()`` prevents the compiler from moving the memory accesses on
48 either side of it to the other side. The compiler barrier has no direct
52 architectures, CPU guarantees are strong enough that blocking compiler
55 compiler barriers.
121 the compiler will not optimize accesses out of existence, create unsolicited
137 - ``qatomic_read()`` and ``qatomic_set()``; these prevent the compiler from
140 stores: both the compiler and the processor are free to reorder
206 ``smp_read_barrier_depends()`` can be just a compiler barrier on
218 also be compiler barriers only.
434 semantics if the compiler supports it, and volatile semantics otherwise.
435 Both semantics prevent the compiler from doing certain transformations;
438 our fingers hoping that the compiler will generate atomic accesses,
481 compiler) before the write of ``x``.