summaryrefslogtreecommitdiffstats
path: root/llvm/lib/Target/AArch64/AArch64TargetTransformInfo.cpp
diff options
context:
space:
mode:
authorSanjoy Das <sanjoy@playingwithpointers.com>2015-10-27 01:36:06 +0000
committerSanjoy Das <sanjoy@playingwithpointers.com>2015-10-27 01:36:06 +0000
commit63d2b7796138144cc6e3a8fb98f9c4b10606ea12 (patch)
treee83503a213c1a723c2526aee48a368699261f9e8 /llvm/lib/Target/AArch64/AArch64TargetTransformInfo.cpp
parent171d6fa35db2ad0d61a5947d4752f431e7baa042 (diff)
downloadbcm5719-llvm-63d2b7796138144cc6e3a8fb98f9c4b10606ea12.tar.gz
bcm5719-llvm-63d2b7796138144cc6e3a8fb98f9c4b10606ea12.zip
[ValueTracking] Don't special case wrapped ConstantRanges; NFCI
Use `getUnsignedMax` directly instead of special casing a wrapped ConstantRange. The previous code would have been "buggy" (and this would have been a semantic change) if LLVM allowed !range metadata to denote full ranges. E.g. in %val = load i1, i1* %ptr, !range !{i1 1, i1 1} ;; == full set ValueTracking would conclude that the high bit (IOW the only bit) in %val was zero. Since !range metadata does not allow empty or full ranges, this change is just a minor stylistic improvement. llvm-svn: 251380
Diffstat (limited to 'llvm/lib/Target/AArch64/AArch64TargetTransformInfo.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud