Ignore IMPLICIT_DEF instructions when computing physreg liveness.

While they appear to provide a normal clobbering def, they don't
in the case of the awkward IMPLICIT_DEF+INSERT_SUBREG idiom. It
would be good to change INSERT_SUBREG; until then, this change
allows post-regalloc scheduling to cope in a mildly conservative
way.

llvm-svn: 60583
This commit is contained in:
Dan Gohman 2008-12-05 05:30:02 +00:00
parent 98463cd44d
commit c1dee225d0
1 changed files with 7 additions and 0 deletions

View File

@ -353,6 +353,13 @@ bool SchedulePostRATDList::BreakAntiDependencies() {
I != E; ++I, --Count) {
MachineInstr *MI = &*I;
// After regalloc, IMPLICIT_DEF instructions aren't safe to treat as
// dependence-breaking. In the case of an INSERT_SUBREG, the IMPLICIT_DEF
// is left behind appearing to clobber the super-register, while the
// subregister needs to remain live. So we just ignore them.
if (MI->getOpcode() == TargetInstrInfo::IMPLICIT_DEF)
continue;
// Check if this instruction has an anti-dependence that we're
// interested in.
DenseMap<MachineInstr *, unsigned>::iterator C = CriticalAntiDeps.find(MI);