RPCS3/llvm
1
0
Fork 0
mirror of https://github.com/RPCS3/llvm.git synced 2026-07-21 03:05:26 -04:00
Code Issues Packages Projects Releases 10 Wiki Activity

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

Browse Source 
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@278033 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Lang Hames
2016-08-08 18:09:56 +00:00
parent cf83621dcd
commit 32217d6ae4
1 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/tutorial/BuildingAJIT3.rst
+6 -6
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: