Be more precise about verifying missing kill flags.

It is legal for an instruction to have two operands using the same register,
only one a kill. This is interpreted as a kill.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@117981 91177308-0d34-0410-b5e6-96231b3b80d8

diff --git a/lib/CodeGen/MachineVerifier.cpp b/lib/CodeGen/MachineVerifier.cpp
index 68688cacabee7e1cd1f10e57de5ecb335e35a36a..8ada60a55331426db1d2b8c0ab9f5864d7b2be5b 100644 (file)
--- a/lib/CodeGen/MachineVerifier.cpp
+++ b/lib/CodeGen/MachineVerifier.cpp
@@ -624,12 +624,14 @@ MachineVerifier::visitMachineOperand(const MachineOperand *MO, unsigned MONum) {
           }
           // Verify isKill == LI.killedAt.
           if (!MI->isRegTiedToDefOperand(MONum)) {
+            // MI could kill register without a kill flag on MO.
+            bool miKill = MI->killsRegister(Reg);
             bool liKill = LI.killedAt(UseIdx.getDefIndex());
-            if (isKill && !liKill) {
+            if (miKill && !liKill) {
               report("Live range continues after kill flag", MO, MONum);
               *OS << "Live range: " << LI << '\n';
             }
-            if (!isKill && liKill) {
+            if (!miKill && liKill) {
               report("Live range ends without kill flag", MO, MONum);
               *OS << "Live range: " << LI << '\n';
             }