Lines Matching refs:assumed
18 - What may not be assumed about memory barriers?
229 And there are a number of things that _must_ or _must_not_ be assumed:
231 (*) It _must_not_ be assumed that the compiler will do what you want with
237 (*) It _must_not_ be assumed that independent loads and stores will be issued
251 (*) It _must_ be assumed that overlapping memory accesses may be merged or
1648 systems because it is assumed that a CPU will appear to be self-consistent,
1821 An ACQUIRE followed by a RELEASE may not be assumed to be full memory barrier
1839 RELEASE may -not- be assumed to be a full memory barrier.
2517 If ordering rules are relaxed, it must be assumed that accesses done inside an
2608 It has to be assumed that the conceptual CPU is weakly-ordered but that it will
2611 frv), and so the most relaxed case (namely DEC Alpha) must be assumed outside
2630 Similarly, it has to be assumed that compiler might reorder the instruction
2932 and assuming no intervention by an external influence, it can be assumed that
2967 assumed that the effect of the storage of V to *A is lost. Similarly: