Lines Matching refs:location

85 store instruction accessing the same location (we ignore complicating
190 store to the same memory location, from any CPU.
222 each CPU stores to its own shared location and then loads from the
223 other CPU's location:
316 gets stored to a shared memory location (or in the case of an array
344 same memory location (the "-loc" suffix).
386 location:
451 dependency if the value obtained by the read affects the location
461 Here the location accessed by the second READ_ONCE() depends on the
463 to address dependencies, since the address of a location accessed
500 For our purposes, a memory location's initial value is treated as
552 of the location's actual size.
560 memory contents.  Specifically, it requires that for each location in
561 shared memory, the stores to that location must form a single global
564 that location.
574 stores reach x's location in memory (or if you prefer a more
584 	W' in program order and they access the same location), where W
601 because it means that the accesses to any single memory location obey
678 related by po.  Coherence order is strictly per-location, or if you
679 prefer, each location has its own independent coherence order.
716 event W for the same location, we will have R ->fr W if and only if
737 to store a certain value at a certain location.  The memory subsystem
741 store falls in the location's coherence order.  In particular, it must
743 other store to the same location which has already propagated to CPU C.
747 same location, that come before R in program order.  If there are, it
752 of the co-latest store to the location in question which has already
896 shared location in memory form a global ordering.  We can imagine
897 inserting the loads from that location into this ordering, by placing
914 hold if the accesses to the fixed memory location can be ordered as
926 as atomic_inc(&x), is atomic?  It means that the memory location (x in
999 data dependency), what location it should be stored into (in the case
1014 a particular location before it knows what that location is.  However,
1032 location.  However, if there is merely a control dependency between R
1045 same location even before it knows what the location's address is.
1049 Two memory accesses of the same location must always be executed in
1055 access the same location), the CPU is obliged to execute W after R.
1105 until it knows what location to load from, i.e., after executing its
1179 W ->coe W'.  This means that W and W' are stores to the same location,
1224 An equally simple case involves two loads of the same location that
1990 1.	they access the same location,
2227 allowed to put plain loads of the same location into the object code.
2250 adding in a store to the same location -- is not allowed.  This is
2252 a concurrent load from that location.  Two concurrent loads don't