diff options
| author | Craig Topper <craig.topper@intel.com> | 2017-12-23 02:54:50 +0000 |
|---|---|---|
| committer | Craig Topper <craig.topper@intel.com> | 2017-12-23 02:54:50 +0000 |
| commit | d6a8f2e67daa3b84e0dd4eb73c7596d65805d91b (patch) | |
| tree | d4e28d380a52dcbf53ad45b1974a1818b29cb3cb /llvm/lib/Analysis/ModuleSummaryAnalysis.cpp | |
| parent | fb59856a4e212c2fe9118138520692c21a1666fe (diff) | |
| download | llvm-d6a8f2e67daa3b84e0dd4eb73c7596d65805d91b.zip llvm-d6a8f2e67daa3b84e0dd4eb73c7596d65805d91b.tar.gz llvm-d6a8f2e67daa3b84e0dd4eb73c7596d65805d91b.tar.bz2 | |
[SelectionDAG][X86] Don't use ->getValueType(0) after a call to getOperand to get the type of the operand.
getOperand returns an SDValue that contains the node and the result number. There is no guarantee that the result number if 0. By using the -> operator we are calling SDNode::getValueType rather than SDValue::getValueType. This requires supplying a result number and we shouldn't assume it was 0.
I don't have a test case. Just noticed while cleaning up some other code and saw that it occurred in other places.
llvm-svn: 321397
Diffstat (limited to 'llvm/lib/Analysis/ModuleSummaryAnalysis.cpp')
0 files changed, 0 insertions, 0 deletions