From 177ced39537286337e965a7d6709bf1d17860b1c Mon Sep 17 00:00:00 2001 From: Dale Johannesen Date: Thu, 11 Feb 2010 18:23:23 +0000 Subject: Allow for more than one DBG_VALUE targeting the same dead instruction. llvm-svn: 95890 --- llvm/lib/CodeGen/DeadMachineInstructionElim.cpp | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'llvm/lib/CodeGen/DeadMachineInstructionElim.cpp') diff --git a/llvm/lib/CodeGen/DeadMachineInstructionElim.cpp b/llvm/lib/CodeGen/DeadMachineInstructionElim.cpp index 6e01e59349e..7ed1a6af180 100644 --- a/llvm/lib/CodeGen/DeadMachineInstructionElim.cpp +++ b/llvm/lib/CodeGen/DeadMachineInstructionElim.cpp @@ -117,10 +117,10 @@ bool DeadMachineInstructionElim::runOnMachineFunction(MachineFunction &MF) { // the former operand will then be deleted normally. if (MI->getNumOperands()==3 && MI->getOperand(0).isReg()) { unsigned Reg = MI->getOperand(0).getReg(); - MachineRegisterInfo::use_iterator I = MRI->use_begin(Reg); - assert(I != MRI->use_end()); - if (++I == MRI->use_end()) - // only one use, which must be this DBG_VALUE. + MachineRegisterInfo::use_nodbg_iterator I = MRI->use_nodbg_begin(Reg); + if (I == MRI->use_nodbg_end()) + // All uses are DBG_VALUEs. Nullify this one; if we find + // others later we will nullify them then. MI->getOperand(0).setReg(0U); } } -- cgit v1.2.3