summaryrefslogtreecommitdiffstats
path: root/llvm/test/Transforms/LoopVectorize/pr31098.ll
diff options
context:
space:
mode:
authorTobias Grosser <tobias@grosser.es>2017-02-12 08:11:12 +0000
committerTobias Grosser <tobias@grosser.es>2017-02-12 08:11:12 +0000
commitb3a85884f7fede38e321a58798007fb600655c24 (patch)
treee62362ef0445d6c7f88593b845418602d911b945 /llvm/test/Transforms/LoopVectorize/pr31098.ll
parent5d91ab46c019223537cc1b9c4c6236e16de71f59 (diff)
downloadbcm5719-llvm-b3a85884f7fede38e321a58798007fb600655c24.tar.gz
bcm5719-llvm-b3a85884f7fede38e321a58798007fb600655c24.zip
Do not use wrapping ranges to bound non-affine accesses
When deriving the range of valid values of a scalar evolution expression might be a range [12, 8), where the upper bound is smaller than the lower bound and where the range is expected to possibly wrap around. We theoretically could model such a range as a union of two non-wrapping ranges, but do not do this as of yet. Instead, we just do not derive any bounds. Before this change, we could have obtained bounds where the maximal possible value is strictly smaller than the minimal possible value, which is incorrect and also caused assertions during scop modeling. llvm-svn: 294891
Diffstat (limited to 'llvm/test/Transforms/LoopVectorize/pr31098.ll')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud