summaryrefslogtreecommitdiffstats
path: root/docs/GetElementPtr.html
diff options
context:
space:
mode:
Diffstat (limited to 'docs/GetElementPtr.html')
-rw-r--r--docs/GetElementPtr.html8
1 files changed, 5 insertions, 3 deletions
diff --git a/docs/GetElementPtr.html b/docs/GetElementPtr.html
index 9e1c8b8..aa874ae 100644
--- a/docs/GetElementPtr.html
+++ b/docs/GetElementPtr.html
@@ -64,7 +64,8 @@
<div class="doc_text">
<p>This document seeks to dispel the mystery and confusion surrounding LLVM's
- GetElementPtr (GEP) instruction. Questions about the wily GEP instruction are
+ <a href="LangRef.html#i_getelementptr">GetElementPtr</a> (GEP) instruction.
+ Questions about the wily GEP instruction are
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.
@@ -653,7 +654,8 @@ idx3 = (char*) &amp;MyVar + 8
<li>Support C, C-like languages, and languages which can be
conceptually lowered into C (this covers a lot).</li>
<li>Support optimizations such as those that are common in
- C compilers.</li>
+ C compilers. In particular, GEP is a cornerstone of LLVM's
+ <a href="LangRef.html#pointeraliasing">pointer aliasing model</a>.</li>
<li>Provide a consistent method for computing addresses so that
address computations don't need to be a part of load and
store instructions in the IR.</li>
@@ -728,7 +730,7 @@ idx3 = (char*) &amp;MyVar + 8
<a href="http://validator.w3.org/check/referer"><img
src="http://www.w3.org/Icons/valid-html401-blue" alt="Valid HTML 4.01"></a>
<a href="http://llvm.org">The LLVM Compiler Infrastructure</a><br/>
- Last modified: $Date: 2010-05-07 02:28:04 +0200 (Fri, 07 May 2010) $
+ Last modified: $Date: 2010-07-06 17:26:33 +0200 (Tue, 06 Jul 2010) $
</address>
</body>
</html>
OpenPOWER on IntegriCloud