Lines Matching refs:variable

458      an ACQUIRE on a given variable, all memory accesses preceding any prior
459      RELEASE on that same variable are guaranteed to be visible.  In other
460      words, within a given variable's critical section, all accesses of all
461      previous critical sections for that variable are guaranteed to have
562 variable B might be stored in an even-numbered cache line.  Then, if the
565 but the old value of the variable B (2).
632 variable 'a' is always non-zero, it would be well within its rights
700 In addition, you need to be careful what you do with the local variable 'q',
722 between the load from variable 'a' and the store to variable 'b'.  It is
802       to the same variable, a barrier() statement is required at the
1275 CPU A follows a load from the same variable executing on CPU B, then
1352      to the same variable, and in some cases, the CPU is within its
1353      rights to reorder loads to the same variable.  This means that
1366      multiple CPUs to a single variable.
1369      the same variable.  Such merging can cause the compiler to "optimize"
1388  (*) The compiler is within its rights to reload a variable, for example,
1391      therefore optimize the variable 'tmp' out of our previous example:
1403      passing a zero to do_something_with() in the case where the variable
1420      the value of variable 'a' is always zero, it can optimize this code:
1432      updating variable 'a'.  If variable 'a' is shared, then the compiler's
1449      variable 'a'.)
1452      if it knows that the variable already has the value being stored.
1454      storing into the variable, which can cause the compiler to do the
1459 	/* Code that does not store to variable a. */
1462      The compiler sees that the value of variable 'a' is already zero, so
1464      surprise if some other CPU might have stored to variable 'a' in the
1471 	/* Code that does not store to variable a. */
1536  (*) The compiler is within its rights to invent stores to a variable,
1553      if variable 'a' was never zero -- when loading variable 'b'.
1612 All that aside, it is never necessary to use ACCESS_ONCE() on a variable
1667      This assigns the value to the variable and then inserts a full memory
1837 RELEASE are to the same lock variable, but only from the perspective of
1846 CPU or task, or (b) the RELEASE and ACQUIRE act on the same variable.
1904 variable, only the first of these alternatives can occur.  In addition,