summaryrefslogtreecommitdiffstats
path: root/llvm/lib/Transforms/Scalar/Sink.cpp
diff options
context:
space:
mode:
authorChandler Carruth <chandlerc@gmail.com>2015-06-17 07:12:40 +0000
committerChandler Carruth <chandlerc@gmail.com>2015-06-17 07:12:40 +0000
commitc41404a09044d241774bf70afe9013dbde751f64 (patch)
tree62ac65b2110508ad0123cffcfecd0493721c6ea4 /llvm/lib/Transforms/Scalar/Sink.cpp
parent9fc7fb274e5341b14c71487cf413343439581d50 (diff)
downloadbcm5719-llvm-c41404a09044d241774bf70afe9013dbde751f64.tar.gz
bcm5719-llvm-c41404a09044d241774bf70afe9013dbde751f64.zip
[PM/AA] Split the location computation out of getArgLocation so the
virtual interface on AliasAnalysis only deals with ModRef information. This interface was both computing memory locations by using TLI and other tricks to estimate the size of memory referenced by an operand, and computing ModRef information through similar investigations. This change narrows the scope of the virtual interface on AliasAnalysis slightly. Note that all of this code could live in BasicAA, and be done with a single investigation of the argument, if it weren't for the fact that the generic code in AliasAnalysis::getModRefBehavior for a callsite calls into the virtual aspect of (now) getArgModRefInfo. But this patch's arrangement seems a not terrible way to go for now. The other interesting wrinkle is how we could reasonably extend LLVM with support for custom memory location sizes and mod/ref behavior for library routines. After discussions with Hal on the review, the conclusion is that this would be best done by fleshing out the much desired support for extensions to TLI, and support these types of queries in that interface where we would likely be doing other library API recognition and analysis. Differential Revision: http://reviews.llvm.org/D10259 llvm-svn: 239884
Diffstat (limited to 'llvm/lib/Transforms/Scalar/Sink.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud