From: Owen Anderson <resistor@mac.com>
Date: Tue, 2 Oct 2007 00:43:25 +0000 (+0000)
Subject: Mention memdep in the AA documentation.
X-Git-Url: http://plrg.eecs.uci.edu/git/?a=commitdiff_plain;h=5a726b8ecfc26cd67b15962be0eabff9a7a20102;p=oota-llvm.git

Mention memdep in the AA documentation.


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

diff --git a/docs/AliasAnalysis.html b/docs/AliasAnalysis.html
index 748b3cb30eb..7c3fa81d443 100644
--- a/docs/AliasAnalysis.html
+++ b/docs/AliasAnalysis.html
@@ -50,6 +50,7 @@
     implementations</a></li>
     </ul>
   </li>
+  <li><a hread="#memdep">Memory Dependence Analysis</a></li>
 </ol>
 
 <div class="doc_author">
@@ -947,6 +948,24 @@ algorithm will have a lower number of may aliases).</p>
 
 </div>
 
+<!-- *********************************************************************** -->
+<div class="doc_section">
+  <a name="memdep">Memory Dependence Analysis</a>
+</div>
+<!-- *********************************************************************** -->
+
+<div class="doc_text">
+
+<p>If you're just looking to be a client of alias analysis information, consider
+using the Memory Dependence Analysis interface instead.  MemDep is a lazy, 
+caching layer on top of alias analysis that is able to answer the question of
+what preceding memory operations a given instruction depends on, either at an
+intra- or inter-block level.  Because of its laziness and caching 
+policy, using MemDep can be a significant performance win over accessing alias
+analysis directly.</p>
+
+</div>
+
 <!-- *********************************************************************** -->
 
 <hr>