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
804       to the same variable, a barrier() statement is required at the
1277 CPU A follows a load from the same variable executing on CPU B, then
1355      to the same variable, and in some cases, the CPU is within its
1356      rights to reorder loads to the same variable.  This means that
1369      accesses from multiple CPUs to a single variable.
1372      the same variable.  Such merging can cause the compiler to "optimize"
1391  (*) The compiler is within its rights to reload a variable, for example,
1394      therefore optimize the variable 'tmp' out of our previous example:
1406      passing a zero to do_something_with() in the case where the variable
1423      the value of variable 'a' is always zero, it can optimize this code:
1435      one updating variable 'a'.  If variable 'a' is shared, then the
1452      variable 'a'.)
1455      if it knows that the variable already has the value being stored.
1457      storing into the variable, which can cause the compiler to do the
1462 	/* Code that does not store to variable a. */
1465      The compiler sees that the value of variable 'a' is already zero, so
1467      surprise if some other CPU might have stored to variable 'a' in the
1474 	/* Code that does not store to variable a. */
1542  (*) The compiler is within its rights to invent stores to a variable,
1559      if variable 'a' was never zero -- when loading variable 'b'.
1619 WRITE_ONCE() on a variable that has been marked volatile.  For example,
1675      This assigns the value to the variable and then inserts a full memory
1854 RELEASE are to the same lock variable, but only from the perspective of