Jakob Stoklund Olesen <stoklund at 2pi.dk> writes:>> Are all of those sibling values guaranteed to ultimately derive from the >> same def, in the sense that they can be traced through copies, phis, >> etc. back to a single instruction? > > They are known the all come from the same value in the original live range from before live range splitting.Ok, that's exactly what I need.> The defining instruction may not exists any longer. It could have been > rematerialized somewhere else. It could also have been PHI.Ok, so in that case the traced-to VNInfo will have a def SlotIndex of Slot_Block or something? -David
On Sep 20, 2012, at 10:59 AM, <dag at cray.com> wrote:> Jakob Stoklund Olesen <stoklund at 2pi.dk> writes: > >>> Are all of those sibling values guaranteed to ultimately derive from the >>> same def, in the sense that they can be traced through copies, phis, >>> etc. back to a single instruction? >> >> They are known the all come from the same value in the original live range from before live range splitting. > > Ok, that's exactly what I need. > >> The defining instruction may not exists any longer. It could have been >> rematerialized somewhere else. It could also have been PHI. > > Ok, so in that case the traced-to VNInfo will have a def SlotIndex of > Slot_Block or something?VNI->isPHIDef()
Jakob Stoklund Olesen <stoklund at 2pi.dk> writes:>> Ok, so in that case the traced-to VNInfo will have a def SlotIndex of >> Slot_Block or something? > > VNI->isPHIDef()Ah, that's what that means. Thanks a bunch for your help! -David