search for: isphidef

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

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

...9;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()

Hi Jonas, Thanks for your patience. After spending some time looking at the additional output you gave me, I agree that your fix is the right one. I was worried that this problem may arise because we were spilling not real user, but in fact what I thought was the problem is an optimization we could do :). See my comments inlined for a few nitpicks before you commit. Thanks again, -Quentin On