maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity

fix some incorrect links. 

llvm-svn: 60919
This commit is contained in:
Chris Lattner 2008-12-12 04:20:01 +00:00
parent a6a9066848
commit e5a6d7ddae
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
llvm/docs/tutorial/OCamlLangImpl3.html
View File

@ -26,7 +26,7 @@
<li><a href="#code">Full Code Listing</a></li> <li><a href="#code">Full Code Listing</a></li>
</ol> </ol>
</li> </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> Support</li>
</ul> </ul>
@ -491,7 +491,7 @@ entry:
</div> </div>
<p>Note how the parser turns the top-level expression into anonymous functions <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 support</a> in the next chapter. Also note that the code is very literally
transcribed, no optimizations are being performed. We will transcribed, no optimizations are being performed. We will
<a href="OCamlLangImpl4.html#trivialconstfold">add optimizations</a> explicitly <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> each other.</p>
<p>This wraps up the third chapter of the Kaleidoscope tutorial. Up next, we'll <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> support</a> to this so we can actually start running code!</p>
</div> </div>