From 91b1289daad4f83345b1d195c9cf8433e458acc9 Mon Sep 17 00:00:00 2001
From: Dan Gohman <gohman@apple.com>
Date: Thu, 18 Feb 2010 18:22:18 +0000
Subject: 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
---
 llvm/docs/AdvancedGetElementPtr.html | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

(limited to 'llvm/docs/AdvancedGetElementPtr.html')

diff --git a/llvm/docs/AdvancedGetElementPtr.html b/llvm/docs/AdvancedGetElementPtr.html
index 1e48bb33dbf..b5efe735538 100644
--- a/llvm/docs/AdvancedGetElementPtr.html
+++ b/llvm/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>
 
-- 
cgit v1.2.3