rust jit wasm webassembly runtime wasi cranelift sandbox wasmtime

History

Dan Gohman fa36e86f2c Update WASI to cap-std 0.25 and windows-sys. (#4302 ) This updates to rustix 0.35.6, and updates wasi-common to use cap-std 0.25 and windows-sys (instead of winapi). Changes include: - Better error code mappings on Windows. - Fixes undefined references to `utimensat` on Darwin. - Fixes undefined references to `preadv64` and `pwritev64` on Android. - Updates to io-lifetimes 0.7, which matches the io_safety API in Rust. - y2038 bug fixes for 32-bit platforms		2 years ago
..
WASI@0ba0c5e2e3	Implement `sock_accept`	3 years ago
cap-std-sync	Update WASI to cap-std 0.25 and windows-sys. (#4302)	2 years ago
src	Update WASI to cap-std 0.25 and windows-sys. (#4302)	2 years ago
tokio	Update WASI to cap-std 0.25 and windows-sys. (#4302)	2 years ago
Cargo.toml	Update WASI to cap-std 0.25 and windows-sys. (#4302)	2 years ago
LICENSE	Initial reorg.	5 years ago
README.md	wasi-common no longer contains code derived from cloudabi-utils	4 years ago
build.rs	Add "cargo:rerun-if-changed=build.rs" to some build.rs files.	3 years ago

README.md

`wasi-common`

A Bytecode Alliance project

A library providing a common implementation of WASI hostcalls for re-use in any WASI-enabled runtime.

The wasi-common crate will ultimately serve as a library providing a common implementation of WASI hostcalls for re-use in any WASI (and potentially non-WASI) runtimes such as Wasmtime and Lucet.

The library is an adaption of lucet-wasi crate from the Lucet project, and it is currently based on 40ae1df git revision.

Please note that the library requires Rust compiler version at least 1.37.0.

Supported syscalls

*nix

In our *nix implementation, we currently support the entire WASI API with the exception of socket hostcalls:

sock_recv
sock_send
sock_shutdown

We expect these to be implemented when network access is standardised.

We also currently do not support the proc_raise hostcall, as it is expected to be dropped entirely from WASI.

Windows

In our Windows implementation, we currently support the minimal subset of WASI API which allows for running the very basic "Hello world!" style WASM apps. More coming shortly, so stay tuned!

Development hints

When testing the crate, you may want to enable and run full wasm32 integration testsuite. This requires wasm32-wasi target installed which can be done as follows using rustup

rustup target add wasm32-wasi

Now, you should be able to run the integration testsuite by running cargo test on the test-programs package with test-programs/test_programs feature enabled:

cargo test --features test-programs/test_programs --package test-programs