Avoid adding PHI arguments for a predecessor that has gone away when a BRCOND was...

[oota-llvm.git] / docs / GetElementPtr.html

diff --git a/docs/GetElementPtr.html b/docs/GetElementPtr.html
index 0684b2c78ae072595c4e053c0562b86f8daa1ff3..dd49ef7ec4c1e47e7c145e8582794c41cb3e94a1 100644 (file)
--- a/docs/GetElementPtr.html
+++ b/docs/GetElementPtr.html
@@ -40,7 +40,7 @@
 <div class="doc_text"> 
   <p>This document seeks to dispel the mystery and confusion surrounding LLVM's
   GetElementPtr (GEP) instruction. Questions about the wiley GEP instruction are
-  probably the most frequently occuring questions once a developer gets down to
+  probably the most frequently occurring questions once a developer gets down to
   coding with LLVM. Here we lay out the sources of confusion and show that the
   GEP instruction is really quite simple.
   </p>
@@ -303,13 +303,14 @@ idx3 = (char*) &amp;MyVar + 8
 </div>
 
   <p>In this example, <tt>idx1</tt> computes the address of the second integer
-  in the array that is in the structure in %MyVar, that is <tt>MyVar+4</tt>. The 
-  type of <tt>idx1</tt> is <tt>i32*</tt>. However, <tt>idx2</tt> computes the 
-  address of <i>the next</i> structure after <tt>%MyVar</tt>. The type of 
-  <tt>idx2</tt> is <tt>{ [10 x i32] }*</tt> and its value is equivalent 
-  to <tt>MyVar + 40</tt> because it indexes past the ten 4-byte integers 
-  in <tt>MyVar</tt>. Obviously, in such a situation, the pointers don't 
-  alias.</p>
+  in the array that is in the structure in <tt>%MyVar</tt>, that is
+  <tt>MyVar+4</tt>. The type of <tt>idx1</tt> is <tt>i32*</tt>. However,
+  <tt>idx2</tt> computes the address of <i>the next</i> structure after
+  <tt>%MyVar</tt>. The type of <tt>idx2</tt> is <tt>{ [10 x i32] }*</tt> and its
+  value is equivalent to <tt>MyVar + 40</tt> because it indexes past the ten
+  4-byte integers in <tt>MyVar</tt>. Obviously, in such a situation, the
+  pointers don't alias.</p>
+
 </div>
 
 <!-- *********************************************************************** -->