Lines Matching refs:MemoryUse

48 - ``MemoryUse``
76 inside ``MemorySSA``, whereas ``Instruction``\ s are mapped to ``MemoryUse``\ s
84 ``MemoryUse``\ s are operations which use but don't modify memory. An example of
85 a ``MemoryUse`` is a ``load``, or a ``readonly`` function call.
107 by either ``b`` or ``c`` (or both).  And finally, ``MemoryUse(x)`` means
110 and ``MemoryUse(x)`` are in the same loop, the use can't
146     ; MemoryUse(5)
150     ; MemoryUse(1)
177 - ``MemoryUse(5)`` notes that ``load i8, i8* %p1`` is a use of memory, and that
181 - ``MemoryUse(1)`` notes that ``load i8, i8* %p3`` is just a user of memory,
228 and ``MemoryUse``\ s by consulting whatever alias analysis stack you happen to
262 ``MemoryUse``\ s keep a single operand, which is their defining or optimized
264 Traditionally ``MemorySSA`` optimized ``MemoryUse``\ s at build-time, up to a
266 Specifically, the operand of every ``MemoryUse`` was optimized to point to the
267 actual clobber of said ``MemoryUse``. This can be seen in the above example; the
268 second ``MemoryUse`` in ``if.end`` has an operand of ``1``, which is a
275 one-time optimization of ``MemoryUse``\ s, if this was not done before.
308 When ``MemoryUse``\ s are optimized, for a given store,  you can find all loads
317       if (auto *MU = cast_of_null<MemoryUse>MA) {
318         // Process MemoryUse as needed.
376     ; MemoryUse(1)
380     ; MemoryUse(1)