Lines Matching refs:compiler
40 any sort of constraint on the compiler's choice of optimizations [3].
42 compiler's use of code-motion and common-subexpression optimizations.
47 data_race(READ_ONCE(a)), which will both restrict compiler optimizations
97 If it is necessary to both restrict compiler optimizations and disable
121 that provides the compiler much less scope for mischievous optimizations.
158 due to compiler-mangled reads, it can also tolerate the occasional
159 compiler-mangled write, at least assuming that the proper value is in
220 compiler, though one could imagine hardened kernel builds treating the
239 of how the compiler has been prevented from optimizing those accesses
260 As noted earlier, the goal is to prevent the compiler from destroying
301 The reader-writer lock prevents the compiler from introducing concurrency
311 If it is necessary to suppress compiler optimization and also detect
623 [3] "Who's afraid of a big bad optimizing compiler?"