summaryrefslogtreecommitdiffstats
path: root/llvm/lib/Transforms/Coroutines
diff options
context:
space:
mode:
authorMatthew Simpson <mssimpso@codeaurora.org>2016-08-29 20:14:04 +0000
committerMatthew Simpson <mssimpso@codeaurora.org>2016-08-29 20:14:04 +0000
commitdf19502b16b59fd6ccfda2ee4a3afa99af31682e (patch)
tree084d24f4a597b9a8eb14c50daa75a218ab0e0bea /llvm/lib/Transforms/Coroutines
parent54695a339f5d4f336865a564ab539ff1b5743223 (diff)
downloadbcm5719-llvm-df19502b16b59fd6ccfda2ee4a3afa99af31682e.tar.gz
bcm5719-llvm-df19502b16b59fd6ccfda2ee4a3afa99af31682e.zip
[LV] Move insertelement sequence after scalar definitions
After r279649 when getting a vector value from VectorLoopValueMap, we create an insertelement sequence on-demand if the value has been scalarized instead of vectorized. We previously inserted this insertelement sequence before the value's first vector user. However, this insert location is problematic if that user is the phi node of a first-order recurrence. With this patch, we move the insertelement sequence after the last scalar instruction we created when scalarizing the value. Thus, the value's vector definition in the new loop will immediately follow its scalar definitions. This should fix PR30183. Reference: https://llvm.org/bugs/show_bug.cgi?id=30183 llvm-svn: 280001
Diffstat (limited to 'llvm/lib/Transforms/Coroutines')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud