[llvm-commits] [llvm] r169546 - /llvm/trunk/docs/GetElementPtr.rst
Dmitri Gribenko
gribozavr at gmail.com
Thu Dec 6 13:12:35 PST 2012
Author: gribozavr
Date: Thu Dec 6 15:12:35 2012
New Revision: 169546
URL: http://llvm.org/viewvc/llvm-project?rev=169546&view=rev
Log:
Documentation: fix typos and formatting.
Modified:
llvm/trunk/docs/GetElementPtr.rst
Modified: llvm/trunk/docs/GetElementPtr.rst
URL: http://llvm.org/viewvc/llvm-project/llvm/trunk/docs/GetElementPtr.rst?rev=169546&r1=169545&r2=169546&view=diff
==============================================================================
--- llvm/trunk/docs/GetElementPtr.rst (original)
+++ llvm/trunk/docs/GetElementPtr.rst Thu Dec 6 15:12:35 2012
@@ -22,7 +22,7 @@
When people are first confronted with the GEP instruction, they tend to relate
it to known concepts from other programming paradigms, most notably C array
indexing and field selection. GEP closely resembles C array indexing and field
-selection, however it's is a little different and this leads to the following
+selection, however it is a little different and this leads to the following
questions.
What is the first index of the GEP instruction?
@@ -190,7 +190,7 @@
structure containing a pointer to an array of 40 ints. The GEP instruction seems
to be accessing the 18th integer of the structure's array of ints. However, this
is actually an illegal GEP instruction. It won't compile. The reason is that the
-pointer in the structure <i>must</i> be dereferenced in order to index into the
+pointer in the structure *must* be dereferenced in order to index into the
array of 40 ints. Since the GEP instruction never accesses memory, it is
illegal.
@@ -416,7 +416,7 @@
Can I compute the distance between two objects, and add that value to one address to compute the other address?
---------------------------------------------------------------------------------------------------------------
-As with arithmetic on null, You can use GEP to compute an address that way, but
+As with arithmetic on null, you can use GEP to compute an address that way, but
you can't use that pointer to actually access the object if you do, unless the
object is managed outside of LLVM.
More information about the llvm-commits
mailing list