Lines Matching refs:compiler

91 	away entirely by the compiler or processor, and explicitly invoke the
92 	appropriate compiler and/or memory barrier for each use case.  Failure
94 	different architectures or compiler optimizations, or even changes in
95 	unrelated code which changes how the compiler optimizes the section
101 and WRITE_ONCE() macros should be used to prevent the compiler from using
110 If the compiler can prove that do_something() does not store to the
111 variable a, then the compiler is within its rights transforming this to
118 If you don't want the compiler to do this (and you probably don't), then
132 If the compiler can prove that do_something_with() does not store to the
133 variable a, then the compiler is within its rights to manufacture an
144 The compiler would be likely to manufacture this additional load if
147 stack and later reload.  To prevent the compiler from attacking your
163 The compiler is within its rights to manufacture an additional store
172 the compiler from doing this, write something like::