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

[BuildingAJIT] Fix a couple of typos in the Chapter 3 draft. 

llvm-svn: 278033
This commit is contained in:
Lang Hames 2016-08-08 18:09:56 +00:00
parent 772d11471c
commit 96a2d57b75
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
llvm/docs/tutorial/BuildingAJIT3.rst
View File

@ -19,14 +19,14 @@ CompileOnDemand layer the JIT from `Chapter 2 <BuildingAJIT2.html>`_.
Lazy Compilation
================
When we add a module to the KaleidoscopeJIT class described in Chapter 2 it is
When we add a module to the KaleidoscopeJIT class from Chapter 2 it is
immediately optimized, compiled and linked for us by the IRTransformLayer,
IRCompileLayer and ObjectLinkingLayer respectively. This scheme, where all the
work to make a Module executable is done up front, is simple to understand its
performance characteristics are easy to reason about. However, it will lead to
very high startup times if the amount of code to be compiled is large, and may
also do a lot of unnecessary compilation if only a few compiled functions are
ever called at runtime. A truly "just-in-time" compiler should allow us to
work to make a Module executable is done up front, is simple to understand and
its performance characteristics are easy to reason about. However, it will lead
to very high startup times if the amount of code to be compiled is large, and
may also do a lot of unnecessary compilation if only a few compiled functions
are ever called at runtime. A truly "just-in-time" compiler should allow us to
defer the compilation of any given function until the moment that function is
first called, improving launch times and eliminating redundant work. In fact,
the ORC APIs provide us with a layer to lazily compile LLVM IR: