mirror of
https://github.com/RPCS3/llvm-mirror.git
synced 2025-01-26 06:04:47 +00:00
Mention memdep in the AA documentation.
llvm-svn: 42519
This commit is contained in:
parent
6b21d8cc55
commit
d98c62147e
@ -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…
x
Reference in New Issue
Block a user