summaryrefslogtreecommitdiffstats
path: root/llvm/lib/Target/ARM/ARMLoadStoreOptimizer.cpp
diff options
context:
space:
mode:
authorPhilip Reames <listmail@philipreames.com>2015-01-26 18:39:52 +0000
committerPhilip Reames <listmail@philipreames.com>2015-01-26 18:39:52 +0000
commit32351455f6fdd9293850f32c5e92ca29d6bf40a0 (patch)
treef7722324be71a23eecb4df63c4e7d09c0a1a6ab1 /llvm/lib/Target/ARM/ARMLoadStoreOptimizer.cpp
parent56a03938f7a536dc2cef3c42ed67b3f218a1c758 (diff)
downloadbcm5719-llvm-32351455f6fdd9293850f32c5e92ca29d6bf40a0.tar.gz
bcm5719-llvm-32351455f6fdd9293850f32c5e92ca29d6bf40a0.zip
Pass QueryInst down through non-local dependency calculation
This change is mostly motivated by exposing information about the original query instruction to the actual scanning work in getPointerDependencyFrom when used by GVN PRE. In a follow up change, I will use this to be more precise with regards to the semantics of volatile instructions encountered in the scan of a basic block. Worth noting, is that this change (despite appearing quite simple) is not semantically preserving. By providing more information to the helper routine, we allow some optimizations to kick in that weren't previously able to (when called from this code path.) In particular, we see that treatment of !invariant.load becomes more precise. In theory, we might see a difference with an ordered/atomic instruction as well, but I'm having a hard time actually finding a test case which shows that. Test wise, I've included new tests for !invariant.load which illustrate this difference. I've also included some updated TBAA tests which highlight that this change isn't needed for that optimization to kick in - it's handled inside alias analysis itself. Eventually, it would be nice to factor the !invariant.load handling inside alias analysis as well. Differential Revision: http://reviews.llvm.org/D6895 llvm-svn: 227110
Diffstat (limited to 'llvm/lib/Target/ARM/ARMLoadStoreOptimizer.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud