replica
/
hanchenye-llvm-project
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Clarify that the rules about object hopping kick in when a pointer is 

deferenced, rather than when the pointer value is computed.

llvm-svn: 96596
This commit is contained in:
Dan Gohman 2010-02-18 18:22:18 +00:00
parent f8b53536ed
commit 91b1289daa
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
llvm/docs/AdvancedGetElementPtr.html
View File

@ -44,10 +44,10 @@
where it doesn't do this. With GEP you can avoid this problem.
<p>Also, GEP carries additional pointer aliasing rules. It's invalid to take a
GEP from one object and address into a different separately allocated
object. IR producers (front-ends) must follow this rule, and consumers
(optimizers, specifically alias analysis) benefit from being able to rely
on it.</p>
GEP from one object, address into a different separately allocated
object, and deference it. IR producers (front-ends) must follow this rule,
and consumers (optimizers, specifically alias analysis) benefit from being
able to rely on it.</p>
<p>And, GEP is more concise in common cases.</p>