forked from OSchip/llvm-project
[Tablegen] Use correct result number variables with the pattern nodes they go with when handling SDTCisSameAs. No functional change as they are always both 0 unless you try to define a multi result type profile that uses SDTCisSame on one of the other results.
llvm-svn: 231226
This commit is contained in:
parent
54a7ca3fcb
commit
483a3000f5
|
@ -901,8 +901,8 @@ bool SDTypeConstraint::ApplyTypeConstraint(TreePatternNode *N,
|
|||
unsigned OResNo = 0;
|
||||
TreePatternNode *OtherNode =
|
||||
getOperandNum(x.SDTCisSameAs_Info.OtherOperandNum, N, NodeInfo, OResNo);
|
||||
return NodeToApply->UpdateNodeType(OResNo, OtherNode->getExtType(ResNo),TP)|
|
||||
OtherNode->UpdateNodeType(ResNo,NodeToApply->getExtType(OResNo),TP);
|
||||
return NodeToApply->UpdateNodeType(ResNo, OtherNode->getExtType(OResNo),TP)|
|
||||
OtherNode->UpdateNodeType(OResNo,NodeToApply->getExtType(ResNo),TP);
|
||||
}
|
||||
case SDTCisVTSmallerThanOp: {
|
||||
// The NodeToApply must be a leaf node that is a VT. OtherOperandNum must
|
||||
|
|
Loading…
Reference in New Issue