mirror of
https://github.com/c64scene-ar/llvm-6502.git
synced 2024-12-14 11:32:34 +00:00
Typo.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@29700 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
parent
eda573ddf9
commit
e3c312fc89
@ -81,7 +81,7 @@
|
|||||||
<p>it is natural to think that there is only one index, the selection of the
|
<p>it is natural to think that there is only one index, the selection of the
|
||||||
field <tt>F</tt>. However, in this example, <tt>Foo</tt> is a pointer. That
|
field <tt>F</tt>. However, in this example, <tt>Foo</tt> is a pointer. That
|
||||||
pointer must be indexed explicitly in LLVM. C, on the other hand, indexs
|
pointer must be indexed explicitly in LLVM. C, on the other hand, indexs
|
||||||
through it ransparently. To arrive at the same address location as the C
|
through it transparently. To arrive at the same address location as the C
|
||||||
code, you would provide the GEP instruction with two index operands. The
|
code, you would provide the GEP instruction with two index operands. The
|
||||||
first operand indexes through the pointer; the second operand indexes the
|
first operand indexes through the pointer; the second operand indexes the
|
||||||
field <tt>F</tt> of the structure, just as if you wrote:</p>
|
field <tt>F</tt> of the structure, just as if you wrote:</p>
|
||||||
|
Loading…
Reference in New Issue
Block a user