summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/python_api/debugger
diff options
context:
space:
mode:
authorFlorian Hahn <flo@fhahn.com>2019-05-30 05:03:12 +0000
committerFlorian Hahn <flo@fhahn.com>2019-05-30 05:03:12 +0000
commite4cfa89915b7e16a095272f6603a3df83b982d38 (patch)
treefd8476c93177e368a72ff38e69bbc0c6b137c216 /lldb/packages/Python/lldbsuite/test/python_api/debugger
parent789b7f0828b08f5c4bf9ff1ff7ef733c73ecdc0a (diff)
downloadbcm5719-llvm-e4cfa89915b7e16a095272f6603a3df83b982d38.tar.gz
bcm5719-llvm-e4cfa89915b7e16a095272f6603a3df83b982d38.zip
[LV] Inform about exactly reason of loop illegality
Currently, only the following information is provided by LoopVectorizer in the case when the CF of the loop is not legal for vectorization: LV: Can't vectorize the instructions or CFG LV: Not vectorizing: Cannot prove legality. But this information is not enough for the root cause analysis; what is exactly wrong with the loop should also be printed: LV: Not vectorizing: The exiting block is not the loop latch. Patch by Pavel Samolysov. Reviewers: mkuper, hsaito, rengolin, fhahn Reviewed By: fhahn Differential Revision: https://reviews.llvm.org/D62311 llvm-svn: 362056
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/debugger')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud