[LAA-memchecks 2/3] Move number of memcheck threshold checking to LV
authorAdam Nemet <anemet@apple.com>
Tue, 10 Mar 2015 18:54:23 +0000 (18:54 +0000)
committerAdam Nemet <anemet@apple.com>
Tue, 10 Mar 2015 18:54:23 +0000 (18:54 +0000)
commit98c4c5dd78f48542fb0712632fe9f4ebc0ae6da6
tree8470d3ca2896c8afbfe47c02cbdd742e3397e6fe
parentb6dc76ffe5c80a51ebb32e964b9d704c58ae170e
[LAA-memchecks 2/3] Move number of memcheck threshold checking to LV

Now the analysis won't "fail" if the memchecks exceed the threshold.  It
is the transform pass' responsibility to perform the check.

This allows the transform pass to further analyze/eliminate the
memchecks.  E.g. in Loop distribution we only need to check pointers
that end up in different partitions.

Note that there is a slight change of functionality here.  The logic in
analyzeLoop is that if dependence checking fails due to non-constant
distance between the pointers, another attempt is made to prove safety
of the dependences purely using run-time checks.

Before this patch we could fail the loop due to exceeding the memcheck
threshold after the first step, now we only check the threshold in the
client after the full analysis.  There is no measurable compile-time
effect but I wanted to record this here.

llvm-svn: 231817
llvm/include/llvm/Analysis/LoopAccessAnalysis.h
llvm/lib/Analysis/LoopAccessAnalysis.cpp
llvm/lib/Transforms/Vectorize/LoopVectorize.cpp