Use the AliasAnalysis interface to determine how a Function accesses
authorDan Gohman <gohman@apple.com>
Tue, 9 Nov 2010 20:13:27 +0000 (20:13 +0000)
committerDan Gohman <gohman@apple.com>
Tue, 9 Nov 2010 20:13:27 +0000 (20:13 +0000)
memory. This isn't a real improvement with present day AliasAnalysis
implementations; it's mainly for consistency.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@118624 91177308-0d34-0410-b5e6-96231b3b80d8

lib/Transforms/IPO/FunctionAttrs.cpp

index 71671d6fe9a5a0d68709aeb208571df430703a09..fcdc5f18f16c1fef5ad685bb340712eef4fe4e19 100644 (file)
@@ -101,14 +101,15 @@ bool FunctionAttrs::AddReadAttrs(const CallGraphSCC &SCC) {
       // External node - may write memory.  Just give up.
       return false;
 
-    if (F->doesNotAccessMemory())
+    AliasAnalysis::ModRefBehavior MRB = AA->getModRefBehavior(F);
+    if (MRB == AliasAnalysis::DoesNotAccessMemory)
       // Already perfect!
       continue;
 
     // Definitions with weak linkage may be overridden at linktime with
     // something that writes memory, so treat them like declarations.
     if (F->isDeclaration() || F->mayBeOverridden()) {
-      if (!F->onlyReadsMemory())
+      if (!AliasAnalysis::onlyReadsMemory(MRB))
         // May write memory.  Just give up.
         return false;