Don't use getSetCCResultType for creating a vselect
authorMatt Arsenault <Matthew.Arsenault@amd.com>
Tue, 10 Sep 2013 00:41:56 +0000 (00:41 +0000)
committerMatt Arsenault <Matthew.Arsenault@amd.com>
Tue, 10 Sep 2013 00:41:56 +0000 (00:41 +0000)
commitc6c08508cab2fc4f52e9ab44dce272e240661e06
tree466b27319ce6856c7b4d883ce06fb5f1813c7097
parentffdee89a3c3b283ac02e6d0522e8e8d461bd3ff1
Don't use getSetCCResultType for creating a vselect

The vselect mask isn't a setcc.

This breaks in the case when the result of getSetCCResultType
is larger than the vector operands

e.g. %tmp = select i1 %cmp <2 x i8> %a, <2 x i8> %b
when getSetCCResultType returns <2 x i32>, the assertion
that the (MaskTy.getSizeInBits() == Op1.getValueType().getSizeInBits())
is hit.

No test since I don't think I can hit this with any of the current
targets. The R600/SI implementation would break, since it returns a
vector of i1 for this, but it doesn't reach ExpandSELECT for other
reasons.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@190376 91177308-0d34-0410-b5e6-96231b3b80d8
lib/CodeGen/SelectionDAG/LegalizeVectorOps.cpp