Files
wasmtime/crates/runtime
Alex Crichton ea3306e74c Use the psm crate to figure out the current stack pointer (#2358)
Currently the runtime needs to acquire the current stack pointer so it
can set a limit for where if the wasm stack goes below that point it
will abort the wasm code. Acquiring the stack pointer is done in a
brittle way right now which involves looking at the address of what we
hope is an on-stack structure. This turns out to not work at all with
ASan as well.

Instead this commit switches to the `psm` crate which is used by the
Rust compiler team for stack manipulation, namely a coarse version of
segmented stacks to avoid stack overflow in the compiler. We don't need
most of the implementation of `psm`, just the `stack_pointer` function,
but it shouldn't be a burden to bring in!

Closes #2344
2020-11-05 07:29:04 -06:00
..
2019-11-08 06:35:40 -08:00
2020-03-23 09:58:08 -07:00

This is the wasmtime-runtime crate, which contains wasm runtime library support, supporting the wasm ABI used by wasmtime-environ, wasmtime-jit, and wasmtime-obj.

This crate does not make a host vs. target distinction; it is meant to be compiled for the target.

Most users will want to use the main wasmtime crate instead of using this crate directly.