Lines Matching refs:compiler
34 any sort of constraint on the compiler's choice of optimizations [2].
36 compiler's use of code-motion and common-subexpression optimizations.
41 data_race(READ_ONCE(a)), which will both restrict compiler optimizations
91 If it is necessary to both restrict compiler optimizations and disable
115 that provides the compiler much less scope for mischievous optimizations.
152 due to compiler-mangled reads, it can also tolerate the occasional
153 compiler-mangled write, at least assuming that the proper value is in
216 of how the compiler has been prevented from optimizing those accesses
237 As noted earlier, the goal is to prevent the compiler from destroying
278 The reader-writer lock prevents the compiler from introducing concurrency
288 If it is necessary to suppress compiler optimization and also detect
597 [2] "Who's afraid of a big bad optimizing compiler?"