Lines Matching refs:InstanceHandle

66 * `wasmtime::runtime::vm::InstanceHandle` - this is the low-level representation of a
69   it'll create an `InstanceHandle` under the hood. This is a very `unsafe` type
73   `InstanceHandle` doesn't know how to deallocate itself and relies on the
79   An `InstanceHandle` is laid out in memory with some Rust-owned values first
83   fields will have more information. After an `InstanceHandle` in memory is a
84   `VMContext`, which will be discussed next. `InstanceHandle` values are the
86   works with. The `wasmtime::Store` holds onto all these `InstanceHandle` values
89   reduced to simply `InstanceHandle` values all talking to themselves.
92   an `InstanceHandle`, that is passed around in JIT code. A `VMContext` does not
95   wasm module it came from. Each `InstanceHandle` has a "shape" of a `VMContext`
278 3. The `InstanceHandle` corresponding to this instance is allocated. How this
280    for pooling). In addition to initialization of the fields of `InstanceHandle`
282    (which as mentioned above is adjacent to the `InstanceHandle` allocation
286 4. At this point the `InstanceHandle` is stored within the `Store`. This is
491     is where `VMContext` and `InstanceHandle` live. This module used to be a