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

deferenced, rather than when the pointer value is computed.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@96596 91177308-0d34-0410-b5e6-96231b3b80d8

diff --git a/docs/AdvancedGetElementPtr.html b/docs/AdvancedGetElementPtr.html
index 1e48bb33dbf52ec8528e76957079911a87f89877..b5efe735538f0037b52a77b219680e363985c479 100644 (file)
--- a/docs/AdvancedGetElementPtr.html
+++ b/docs/AdvancedGetElementPtr.html
@@ -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>