summaryrefslogtreecommitdiffstats
path: root/llvm/test/CodeGen/Mips/interrupt-attr-args-fail.ll
diff options
context:
space:
mode:
authorJames Molloy <james.molloy@arm.com>2015-10-26 14:10:46 +0000
committerJames Molloy <james.molloy@arm.com>2015-10-26 14:10:46 +0000
commit493e57de01ecabc7af76a64cf39992d12efffca0 (patch)
tree6a524f15cbe479cc42077eb3f8d2970fca1e2e99 /llvm/test/CodeGen/Mips/interrupt-attr-args-fail.ll
parent018f5a7e0bc0da615108843b5e0d7202c7d89f53 (diff)
downloadbcm5719-llvm-493e57de01ecabc7af76a64cf39992d12efffca0.tar.gz
bcm5719-llvm-493e57de01ecabc7af76a64cf39992d12efffca0.zip
[ValueTracking] Extend r251146 to catch a fairly common case
Even though we may not know the value of the shifter operand, it's possible we know the shifter operand is non-zero. This can allow us to infer more known bits - for example: %1 = load %p !range {1, 5} %2 = shl %q, %1 We don't know %1, but we do know that it is nonzero so %2[0] is known zero, and importantly %2 is known non-zero. Calling isKnownNonZero is nontrivially expensive so use an Optional to run it lazily and cache its result. llvm-svn: 251294
Diffstat (limited to 'llvm/test/CodeGen/Mips/interrupt-attr-args-fail.ll')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud