Lines Matching full:volatile
37 minimal intrinsics were provided, and <code>volatile</code> was used in some
49 <li>Proper semantics for Java-style memory, for both <code>volatile</code> and
58 <p>Atomic and volatile in the IR are orthogonal; "volatile" is the C/C++
59 volatile, which ensures that every volatile load and store happens and is
63 be erased. This transformation is not allowed for a pair of volatile
64 stores. On the other hand, a non-volatile non-atomic load can be moved
65 across a volatile load freely, but not an Acquire load.</p>
207 volatile loads and stores are not properly atomic; do not try to use
208 them as a substitute. (Per the C/C++ standards, volatile does provide
427 Java volatile, and the gcc-compatible <code>__sync_*</code> builtins
462 <li>isSimple(): A load or store which is not volatile or atomic. This is
465 <li>isUnordered(): A load or store which is not volatile and at most
469 that they return true for any operation which is volatile or at least
514 volatile; this is not correct in the IR sense of volatile, but CodeGen
515 handles anything marked volatile very conservatively. This should get
