RPCS3/llvm
1
0
Fork 0
mirror of https://github.com/RPCS3/llvm.git synced 2025-02-01 00:02:16 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Fix a thinko noticed by Chandler Carruth.

Browse Source 
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@29724 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Reid Spencer 2006-08-16 05:53:32 +00:00
parent 2e40ae4de6
commit 1014647e40
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
docs/GetElementPtr.html
View File

@ -112,8 +112,9 @@
<p>In this "C" example, the front end compiler (llvm-gcc) will generate three <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 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 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 of these GEP instructions. The second operand indexes through that pointer.
the <tt>struct munger_struct</tt> type, for either the <tt>f1</tt> or 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 <tt>f2</tt> field. So, in LLVM assembly the <tt>munge</tt> function looks
like:</p> like:</p>
<pre> <pre>