summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/expression_command/call-function/TestCallStopAndContinue.py
diff options
context:
space:
mode:
authorAnna Thomas <anna@azul.com>2017-04-11 21:02:00 +0000
committerAnna Thomas <anna@azul.com>2017-04-11 21:02:00 +0000
commit00dc1b74b79a7294d4dc878b76960a0de8f40e38 (patch)
treeff2fe3c08e9827be5abf133c2b9c61dd27a146da /lldb/packages/Python/lldbsuite/test/expression_command/call-function/TestCallStopAndContinue.py
parentf0cb5a80adc79281ab1fe7c514311c23fb5889d2 (diff)
downloadbcm5719-llvm-00dc1b74b79a7294d4dc878b76960a0de8f40e38.tar.gz
bcm5719-llvm-00dc1b74b79a7294d4dc878b76960a0de8f40e38.zip
[LV] Avoid vectorizing first order recurrence when phi uses are outside loop
In the vectorization of first order recurrence, we vectorize such that the last element in the vector will be the one extracted to pass into the scalar remainder loop. However, this is not true when there is a phi (other than the primary induction variable) is used outside the loop. In such a case, we need the value from the second last iteration (i.e. the phi value), not the last iteration (which would be the phi update). I've added a test case for this. Also see PR32396. A follow up patch would generate the correct code gen for such cases, and turn this vectorization on. Differential Revision: https://reviews.llvm.org/D31910 Reviewers: mssimpso llvm-svn: 299985
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/expression_command/call-function/TestCallStopAndContinue.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud