Lines Matching refs:compiler

6 help you prevent your compiler from breaking your code.  However,
9 your own code, even in the absence of help from your compiler.
41 WRITE_ONCE() are optional.  Without the READ_ONCE(), the compiler might
43 the compiler might fuse the store to "b" with other stores.  Worse yet,
44 the compiler might convert the store into a load and a check followed
45 by a store, and this compiler-generated load would not be ordered by
48 Furthermore, if the compiler is able to prove that the value of variable
56 In particular, although READ_ONCE() does force the compiler to emit a
57 load, it does *not* force the compiler to actually use the loaded value.
90 assembly code, after all of the compiler and link-time optimizations
115 The initial READ_ONCE() is still required to prevent the compiler from
119 variable "q", otherwise the compiler might be able to guess the value
132 If MAX is compile-time defined to be 1, then the compiler knows that
134 The compiler is therefore within its rights to transform the above code
160 values were identical, the compiler could pull this store outside of the
171 always true, the compiler can transform this example as follows, again
178 compiler from out-guessing your code.  Again, although READ_ONCE() really
179 does force the compiler to emit code for a given load, the compiler is
195 compiler cannot reorder volatile accesses and also cannot reorder
197 of reasoning, the compiler might compile the two writes to "b" as
237       conditional must involve the prior load.  If the compiler is able
242   (*) Control dependencies require that the compiler avoid reordering the