forked from OSchip/llvm-project
Support for i1 XOR in FastISel. It is actually safe because
i1 operands are assumed to already by zero-extended. llvm-svn: 56615
This commit is contained in:
parent
6975c36c43
commit
5e490a7567
|
@ -135,10 +135,11 @@ bool FastISel::SelectBinaryOp(User *I, ISD::NodeType ISDOpcode) {
|
|||
// under the assumption that i64 won't be used if the target doesn't
|
||||
// support it.
|
||||
if (!TLI.isTypeLegal(VT)) {
|
||||
// MVT::i1 is special. Allow AND and OR (but not XOR) because they
|
||||
// MVT::i1 is special. Allow AND, OR, or XOR because they
|
||||
// don't require additional zeroing, which makes them easy.
|
||||
if (VT == MVT::i1 &&
|
||||
(ISDOpcode == ISD::AND || ISDOpcode == ISD::OR))
|
||||
(ISDOpcode == ISD::AND || ISDOpcode == ISD::OR ||
|
||||
ISDOpcode == ISD::XOR))
|
||||
VT = TLI.getTypeToTransformTo(VT);
|
||||
else
|
||||
return false;
|
||||
|
|
Loading…
Reference in New Issue