Lines Matching refs:our

36 added to it. In this Chapter we will make optimization a phase of our JIT
38 layers, but in the long term making optimization part of our JIT will yield an
41 optimization managed by our JIT will allow us to optimize lazily too, rather
42 than having to do all our optimization up-front.
44 To add optimization support to our JIT we will take the KaleidoscopeJIT from
79 but after the CompileLayer we introduce a typedef for our optimization function.
82 our optimization function typedef in place we can declare our OptimizeLayer,
83 which sits on top of our CompileLayer.
85 To initialize our OptimizeLayer we pass it a reference to the CompileLayer
122 OptimizeLayer in our key methods: addModule, findSymbol, and removeModule. In
124 inside our resolver, and the call through to addModuleSet.
147 At the bottom of our JIT we add a private method to do the actual optimization:
156 addModule the OptimizeLayer will call our optimizeModule function before passing
158 called optimizeModule directly in our addModule function and not gone to the
216 "transform functor" (in our case a std::function) respectively. This class is
251 |                  | below. In our REPL this is our default way to search for  |
258 |   findSymbolIn   | we just pass this query on to the layer below. In our     |
316 Here is the complete code listing for our running example with an
331 .. [1] When we add our top-level expression to the JIT, any calls to functions