aboutsummaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorReid Spencer <rspencer@reidspencer.com>2006-08-16 05:53:32 +0000
committerReid Spencer <rspencer@reidspencer.com>2006-08-16 05:53:32 +0000
commit1014647e40020a67da79db6732168b7c7d85dbe0 (patch)
treef516405ae33158c91a5362031c9dd897933157dd /docs
parent2e40ae4de67ba37d02281d51e7dfd629205e1e30 (diff)
Fix a thinko noticed by Chandler Carruth.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@29724 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'docs')
-rw-r--r--docs/GetElementPtr.html5
1 files changed, 3 insertions, 2 deletions
diff --git a/docs/GetElementPtr.html b/docs/GetElementPtr.html
index 05d74e248e..4e3c761118 100644
--- a/docs/GetElementPtr.html
+++ b/docs/GetElementPtr.html
@@ -112,8 +112,9 @@
<p>In this "C" example, the front end compiler (llvm-gcc) will generate three
GEP instructions for the three indices through "P" in the assignment
statement. The function argument <tt>P</tt> will be the first operand of each
- of these GEP instructions. The second operand will be the field offset into
- the <tt>struct munger_struct</tt> type, for either the <tt>f1</tt> or
+ of these GEP instructions. The second operand indexes through that pointer.
+ The third operand will be the field offset into the
+ <tt>struct munger_struct</tt> type, for either the <tt>f1</tt> or
<tt>f2</tt> field. So, in LLVM assembly the <tt>munge</tt> function looks
like:</p>
<pre>