summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/python_api/thread/main.cpp
diff options
context:
space:
mode:
authorCong Hou <congh@google.com>2015-12-15 22:45:09 +0000
committerCong Hou <congh@google.com>2015-12-15 22:45:09 +0000
commita73ffa2206118505790a0d0eff7f6b34fcc5722e (patch)
tree82aaa962320ca159af55d7beeac698b700d85515 /lldb/packages/Python/lldbsuite/test/python_api/thread/main.cpp
parentdb87d5dbfdc8fe7322d96984e2b7a0cb242e4c19 (diff)
downloadbcm5719-llvm-a73ffa2206118505790a0d0eff7f6b34fcc5722e.tar.gz
bcm5719-llvm-a73ffa2206118505790a0d0eff7f6b34fcc5722e.zip
[LoopVectorizer] Refine loop vectorizer's register usage calculator by ignoring specific instructions.
(This is the third attempt to check in this patch, and the first two are r255454 and r255460. The once failed test file reg-usage.ll is now moved to test/Transform/LoopVectorize/X86 directory with target datalayout and target triple indicated.) LoopVectorizationCostModel::calculateRegisterUsage() is used to estimate the register usage for specific VFs. However, it takes into account many instructions that won't be vectorized, such as induction variables, GetElementPtr instruction, etc.. This makes the loop vectorizer too conservative when choosing VF. In this patch, the induction variables that won't be vectorized plus GetElementPtr instruction will be added to ValuesToIgnore set so that their register usage won't be considered any more. Differential revision: http://reviews.llvm.org/D15177 llvm-svn: 255691
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/thread/main.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud