LoopVectorizer: Cleanup of miminimum/maximum pattern match code
No need for setting the operands. The pointers are going to be bound by the matcher. radar://13723044 llvm-svn: 181142
This commit is contained in:
parent
a670a0a3aa
commit
f5183729db
|
@ -2991,8 +2991,8 @@ LoopVectorizationLegality::isMinMaxSelectCmpPattern(Instruction *I, ReductionIns
|
|||
if (!Cmp->hasOneUse())
|
||||
return ReductionInstDesc(false, I);
|
||||
|
||||
Value *CmpLeft = Cmp->getOperand(0);
|
||||
Value *CmpRight = Cmp->getOperand(1);
|
||||
Value *CmpLeft;
|
||||
Value *CmpRight;
|
||||
|
||||
// Look for a min/max pattern.
|
||||
if (m_UMin(m_Value(CmpLeft), m_Value(CmpRight)).match(Select))
|
||||
|
|
Loading…
Reference in New Issue