[ModuloSchedule] Fix data types in ModuloScheduleExpander::isLoopCarried

[masakiarai]

Summary

The cycle values in modulo scheduling results can be negative.
The result of ModuloSchedule::getCycle() must be received as an int type.

[ThomasRaoux]

Thanks for catching that!

[masakiarai]

Thank you very much for your quick review.
I don't have commit access.
Could you commit this patch?

[ThomasRaoux]

In D71122#1774935, @masakiarai wrote:

Thank you very much for your quick review.
I don't have commit access.
Could you commit this patch?

Committed:
https://github.com/llvm/llvm-project/commit/caabb713ea157f8c449c8d3eb00410bbef734a22

llvm/lib/CodeGen/ModuloSchedule.cpp

if (ReplaceReg) {
       UseOp.setReg(ReplaceReg);
     }
   }
 }
 
 bool ModuloScheduleExpander::isLoopCarried(MachineInstr &Phi) {
   if (!Phi.isPHI())
     return false;
-  unsigned DefCycle = Schedule.getCycle(&Phi);
+  int DefCycle = Schedule.getCycle(&Phi);
   int DefStage = Schedule.getStage(&Phi);
 
   unsigned InitVal = 0;
   unsigned LoopVal = 0;
   getPhiRegs(Phi, Phi.getParent(), InitVal, LoopVal);
   MachineInstr *Use = MRI.getVRegDef(LoopVal);
   if (!Use || Use->isPHI())
     return true;
-  unsigned LoopCycle = Schedule.getCycle(Use);
+  int LoopCycle = Schedule.getCycle(Use);
   int LoopStage = Schedule.getStage(Use);
   return (LoopCycle > DefCycle) || (LoopStage <= DefStage);
 }
 
 //===----------------------------------------------------------------------===//
 // PeelingModuloScheduleExpander implementation
 //===----------------------------------------------------------------------===//
 // This is a reimplementation of ModuloScheduleExpander that works by creating