Lines Matching refs:MemoryPhi

47 - ``MemoryPhi``
55 ``MemoryDef/MemoryPhi`` which is the version of memory that the new
71 ``MemoryPhi``\ s are ``PhiNode``\ s, but for memory operations. If at any
74 ``MemoryPhi``. As in LLVM IR, ``MemoryPhi``\ s don't correspond to any
75 concrete operation. As such, ``BasicBlock``\ s are mapped to ``MemoryPhi``\ s
105 In the same manner, ``a = MemoryPhi({BB1,b},{BB2,c})`` means that
116 a value (i.e. ``MemoryDef/MemoryPhi``),
131     ; 6 = MemoryPhi({entry,1},{if.end,4})
145     ; 5 = MemoryPhi({if.then,2},{if.else,3})
160 %p1`` in LLVM with ``%1``). Again, ``MemoryPhi``\ s don't correspond to any LLVM
161 Instruction, so the line directly below a ``MemoryPhi`` isn't special.
165 - ``6 = MemoryPhi({entry,1},{if.end,4})`` notes that, when entering
167   ``MemoryPhi`` is referred to in the textual IR by the number ``6``.
169   and its reaching definition before it is ``6``, or the ``MemoryPhi`` after
172   disambiguated ``MemoryPhi``.)
175 - ``5 = MemoryPhi({if.then,2},{if.else,3})`` notes that the clobber before
231 queries ``GlobalsAA``, one that always stops at ``MemoryPhi`` nodes, etc).
243 ``MemoryDef`` or ``MemoryPhi`` of said ``MemoryDef``.
273 ``MemorySSA`` only places ``MemoryPhi``\ s where they're actually
289     ; 3 = MemoryPhi({%0,1},{if.end,2})
308 Because we removed the stores from ``if.then`` and ``if.else``, a ``MemoryPhi``
311 a ``MemoryPhi`` for ``if.end``.
313 If it turns out that this is a large burden, we can just place ``MemoryPhi``\ s