[llvm-commits] [llvm] r42519 - /llvm/trunk/docs/AliasAnalysis.html

[Owen Anderson]

Author: resistor
Date: Mon Oct  1 19:43:25 2007
New Revision: 42519

URL: http://llvm.org/viewvc/llvm-project?rev=42519&view=rev
Log:
Mention memdep in the AA documentation.

Modified:
    llvm/trunk/docs/AliasAnalysis.html

Modified: llvm/trunk/docs/AliasAnalysis.html
URL: http://llvm.org/viewvc/llvm-project/llvm/trunk/docs/AliasAnalysis.html?rev=42519&r1=42518&r2=42519&view=diff

==============================================================================
--- llvm/trunk/docs/AliasAnalysis.html (original)
+++ llvm/trunk/docs/AliasAnalysis.html Mon Oct  1 19:43:25 2007
@@ -50,6 +50,7 @@
     implementations</a></li>
     </ul>
   </li>
+  <li><a hread="#memdep">Memory Dependence Analysis</a></li>
 </ol>
 
 <div class="doc_author">
@@ -948,6 +949,24 @@
 </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>
 <address>