rust jit wasm webassembly runtime wasi cranelift sandbox wasmtime

History

Alex Crichton e9d62746ef Fix writes being flushed to stdio (#7441 ) * Fix writes being flushed to stdio This commit fixes an accidental issue with writing to stdout with the `wasi-common` implementation where writes were line-buffered by the Rust standard library rather than being flushed out immediately as WASI semantics required. Closes #7437 * Fix warning in test		1 year ago
..
WASI@0ba0c5e2e3	Implement `sock_accept`	3 years ago
cap-std-sync	Fix writes being flushed to stdio (#7441)	1 year ago
src	Update preview1 to trap on misaligned pointers (#6776)	1 year ago
tests/all	Fix file writes in preview 2 implementation (#7394)	1 year ago
tokio	Change preview2 builder methods to use `&mut self` (#6770)	1 year ago
Cargo.toml	Refactor the test-programs test suite (#7182)	1 year ago
LICENSE	Initial reorg.	5 years ago
README.md	Implement the remaining socket-related WASI functions. (#4776)	2 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 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