Lines Matching refs:compiled

120 * `wasmtime::Module` - this is the representation of a compiled WebAssembly
122   compiled to native JIT code. `Module` holds the results of said compilation,
130   functions themselves are actually compiled. This holds the internal type
156 2. Next all functions within a module are validated and compiled in parallel.
157    No inter-procedural analysis is done and each function is compiled as its
163    (`wasmtime_environ::Module`), compiled JIT code (stored as an ELF image), and
185 share the same compiled code. Additionally a `wasmtime::Module` is one of the
189 Note that the property of sharing a module's compiled code across all
190 instantiations has interesting implications on what the compiled code can
195 many stores its same function type may take on many values, so the compiled
197 information later). The general gist though is that compiled code leans
207 is compiled with native ABIs (e.g. params/results in registers according to
211 This problem is what the trampolines compiled into a module solve, which is to
226 Each compiled module contains its own set of trampolines, and if two compiled
241 `wasmtime::Engine` level. Modules are compiled into an `Engine`. Insertion of a
253 Once a module has been compiled it's typically then instantiated to actually
517 * `wasmtime-obj` - implementation of creating an ELF image from compiled