You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
Jakub Konka 60d55a3483 Remove a runaway explicit drop 4 years ago
..
WASI@2b027d91c2 latest wasi submodule has witx 0.8.5, required for the error_types iter 5 years ago
src Remove a runaway explicit drop 4 years ago
wig Wasmtime 0.18.0 and Cranelift 0.65.0. 4 years ago
winx Wasmtime 0.18.0 and Cranelift 0.65.0. 4 years ago
yanix Wasmtime 0.18.0 and Cranelift 0.65.0. 4 years ago
Cargo.toml Wasmtime 0.18.0 and Cranelift 0.65.0. 4 years ago
LICENSE Initial reorg. 5 years ago
LICENSE.cloudabi-utils Initial reorg. 5 years ago
README.md Fixes for cargo publish (#1416) 5 years ago
build.rs Move back to only one WASI submodule (#1434) 5 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.

Crates.io version Download docs.rs docs

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

Third-Party Code

Significant parts of our hostcall implementations are derived from the C implementations in cloudabi-utils. See LICENSE.cloudabi-utils for license information.