[llvm-commits] [llvm] r96596 - /llvm/trunk/docs/AdvancedGetElementPtr.html

[Dan Gohman]

Author: djg
Date: Thu Feb 18 12:22:18 2010
New Revision: 96596

URL: http://llvm.org/viewvc/llvm-project?rev=96596&view=rev
Log:
Clarify that the rules about object hopping kick in when a pointer is
deferenced, rather than when the pointer value is computed.

Modified:
    llvm/trunk/docs/AdvancedGetElementPtr.html

Modified: llvm/trunk/docs/AdvancedGetElementPtr.html
URL: http://llvm.org/viewvc/llvm-project/llvm/trunk/docs/AdvancedGetElementPtr.html?rev=96596&r1=96595&r2=96596&view=diff

==============================================================================
--- llvm/trunk/docs/AdvancedGetElementPtr.html (original)
+++ llvm/trunk/docs/AdvancedGetElementPtr.html Thu Feb 18 12:22:18 2010
@@ -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>