Files

Ulrich Weigand 1a865fb0f5 Fix WASI fd_readdir on big-endian (#3016 )

This code assumes that the Dirent structure has the same memory
layout on the host (Rust code) as in wasm code.  This is not true
if the host is big-endian, as wasm is always little-endian.

Fixed by always byte-swapping Dirent fields to little-endian
before passing them on to wasm code.

2021-06-22 10:39:38 -05:00

cap-std-sync

Include READMEs in crates (#2987 )

2021-06-15 06:40:45 -07:00

src

Fix WASI fd_readdir on big-endian (#3016 )

2021-06-22 10:39:38 -05:00

tokio

Bump to 0.28.0 (#2972 )

2021-06-09 14:00:13 -05:00

WASI @ ef8c1a53fe

Update submodules

2021-02-18 14:45:20 -08:00

build.rs

theres the bug

2021-02-04 15:38:02 -08:00

Cargo.toml

Include READMEs in crates (#2987 )

2021-06-15 06:40:45 -07:00

LICENSE

Initial reorg.

2019-11-08 06:35:40 -08:00

README.md

wasi-common no longer contains code derived from cloudabi-utils

2021-01-29 13:28:13 -08:00

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