summaryrefslogtreecommitdiffstats
path: root/llvm/lib/Target
diff options
context:
space:
mode:
authorWei Mi <wmi@google.com>2016-11-15 17:34:52 +0000
committerWei Mi <wmi@google.com>2016-11-15 17:34:52 +0000
commitd2948cef705997c38799a2cc8cba15d809fbf364 (patch)
tree66e0652d285b810c4eaf8f4ae173114b183d9616 /llvm/lib/Target
parent6d279e8e98f83dc1ed8769b1be2a846daef2e33d (diff)
downloadbcm5719-llvm-d2948cef705997c38799a2cc8cba15d809fbf364.tar.gz
bcm5719-llvm-d2948cef705997c38799a2cc8cba15d809fbf364.zip
[IndVars] Change the order to compute WidenAddRec in widenIVUse.
When both WidenIV::getWideRecurrence and WidenIV::getExtendedOperandRecurrence return non-null but different WideAddRec, if getWideRecurrence is called before getExtendedOperandRecurrence, we won't bother to call getExtendedOperandRecurrence again. But As we know it is possible that after SCEV folding, we cannot prove the legality using the SCEVAddRecExpr returned by getWideRecurrence. Meanwhile if getExtendedOperandRecurrence returns non-null WideAddRec, we know for sure that it is legal to do widening for current instruction. So it is better to put getExtendedOperandRecurrence before getWideRecurrence, which will increase the chance of successful widening. Differential Revision: https://reviews.llvm.org/D26059 llvm-svn: 286987
Diffstat (limited to 'llvm/lib/Target')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud