Add suppport for ConstantExprs of shufflevectors whose result type is not equal to the

[oota-llvm.git] / docs / tutorial / OCamlLangImpl3.html

diff --git a/docs/tutorial/OCamlLangImpl3.html b/docs/tutorial/OCamlLangImpl3.html
index b396ef07ae5ccf6fa5b9dcb604a60c4a05a366f8..9caae435e29e149c8017d1d51b106afe849e8ae8 100644 (file)
--- a/docs/tutorial/OCamlLangImpl3.html
+++ b/docs/tutorial/OCamlLangImpl3.html
@@ -26,7 +26,7 @@
     <li><a href="#code">Full Code Listing</a></li>
   </ol>
 </li>
-<li><a href="LangImpl4.html">Chapter 4</a>: Adding JIT and Optimizer
+<li><a href="OCamlLangImpl4.html">Chapter 4</a>: Adding JIT and Optimizer
 Support</li>
 </ul>
 
@@ -148,7 +148,7 @@ internally (<tt>APFloat</tt> has the capability of holding floating point
 constants of <em>A</em>rbitrary <em>P</em>recision).  This code basically just
 creates and returns a <tt>ConstantFP</tt>.  Note that in the LLVM IR
 that constants are all uniqued together and shared.  For this reason, the API
-uses "the foo::get(..)" idiom instead of "new foo(..)" or "foo::create(..)".</p>
+uses "the foo::get(..)" idiom instead of "new foo(..)" or "foo::Create(..)".</p>
 
 <div class="doc_code">
 <pre>
@@ -491,7 +491,7 @@ entry:
 </div>
 
 <p>Note how the parser turns the top-level expression into anonymous functions
-for us.  This will be handy when we add <a href="LangImpl4.html#jit">JIT
+for us.  This will be handy when we add <a href="OCamlLangImpl4.html#jit">JIT
 support</a> in the next chapter.  Also note that the code is very literally
 transcribed, no optimizations are being performed.  We will
 <a href="OCamlLangImpl4.html#trivialconstfold">add optimizations</a> explicitly
@@ -599,7 +599,7 @@ generated.  Here you can see the big picture with all the functions referencing
 each other.</p>
 
 <p>This wraps up the third chapter of the Kaleidoscope tutorial.  Up next, we'll
-describe how to <a href="LangImpl4.html">add JIT codegen and optimizer
+describe how to <a href="OCamlLangImpl4.html">add JIT codegen and optimizer
 support</a> to this so we can actually start running code!</p>
 
 </div>