mirror of
https://github.com/RPCSX/llvm.git
synced 2024-11-24 12:19:53 +00:00
Mention memdep in the AA documentation.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@42519 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
parent
d6f8ee7120
commit
5a726b8ecf
@ -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>
|
||||
|
Loading…
Reference in New Issue
Block a user