Lines Matching refs:load
12 Therefore, a load-load control dependency will not preserve ordering
20 are permitted to predict the result of the load from "b". This prediction
21 can cause other CPUs to see this load as having happened before the load
32 (usually) guaranteed for load-store control dependencies, as in the
42 fuse the load from "a" with other loads. Without the WRITE_ONCE(),
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
57 load, it does *not* force the compiler to actually use the loaded value.
78 WRITE_ONCE(b, 1); /* BUG: No ordering vs. load from a!!! */
87 Now there is no conditional between the load from "a" and the store to
142 between the load from variable "a" and the store to variable "b". It is
149 BUILD_BUG_ON(MAX <= 1); /* Order load from a with store to b. */
179 does force the compiler to emit code for a given load, the compiler is
210 ordered CPU would have no dependency of any sort between the load from
236 between the prior load and the subsequent store, and this
237 conditional must involve the prior load. If the compiler is able