diff options
author | Sanjay Patel <spatel@rotateright.com> | 2019-05-09 13:43:22 +0000 |
---|---|---|
committer | Sanjay Patel <spatel@rotateright.com> | 2019-05-09 13:43:22 +0000 |
commit | 012adfbb96cb5251fe5a520f909d0e19eaf4a492 (patch) | |
tree | d408faca9007ac4e060ec673a09512838ca69fb6 /lldb/packages/Python/lldbsuite/test/python_api/debugger/TestDebuggerAPI.py | |
parent | bc1c6a0b4494d5d89acca67d518be400d42ea71f (diff) | |
download | bcm5719-llvm-012adfbb96cb5251fe5a520f909d0e19eaf4a492.tar.gz bcm5719-llvm-012adfbb96cb5251fe5a520f909d0e19eaf4a492.zip |
[LoopVectorizer] fix test file to not run the entire -O3 pipeline
This test file has a long history of edits from changes outside
of vectorization, and it would happen again with the proposal in
D61726.
End-to-end testing shouldn't be happening in a test file that is
specifically checking for vector masked load/store ops.
Larger-scale testing goes in PhaseOrdering or the test-suite.
I've hopefully preserved the intent by taking what was completely
unoptimized IR in some tests and passing that through the -O1
pipeline. That becomes the input IR, and now we just run the loop
vectorizer and verify that the vector masked ops are produced as
expected.
llvm-svn: 360340
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/debugger/TestDebuggerAPI.py')
0 files changed, 0 insertions, 0 deletions