Files

Pat Hickey 2702619427 wiggle: allow disable tracing in Wiggle-generated code (#5146 )

Wiggle generates code that instruments APIs with tracing code. This is
handy for diagnosing issues at runtime, but when inspecting the output
of Wiggle, it can make the generated code difficult for a human to
decipher. This change makes tracing a default but optional feature,
allowing users to avoid tracing code with commands like `cargo expand
--no-default-features`. This should be no change for current crates
depending on `wiggle`, `wiggle-macro`, and `wiggle-generate`.

review: add 'tracing' feature to wasi-common

review: switch to using macro configuration parsing

Co-authored-by: Andrew Brown <andrew.brown@intel.com>

2022-10-27 11:26:54 -07:00

cap-std-sync

Leverage Cargo's workspace inheritance feature (#4905 )

2022-09-26 11:30:01 -05:00

src

wiggle: allow disable tracing in Wiggle-generated code (#5146 )

2022-10-27 11:26:54 -07:00

tokio

wiggle: make wasmtime a mandatory dep, get rid of own Trap enum (#5137 )

2022-10-27 09:28:10 -07:00

WASI @ 0ba0c5e2e3

Implement sock_accept

2022-01-31 16:25:11 -08:00

build.rs

Add "cargo:rerun-if-changed=build.rs" to some build.rs files.

2021-09-16 11:52:21 -07:00

Cargo.toml

wiggle: make wasmtime a mandatory dep, get rid of own Trap enum (#5137 )

2022-10-27 09:28:10 -07:00

LICENSE

Initial reorg.

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

README.md

Implement the remaining socket-related WASI functions. (#4776 )

2022-08-26 11:39:51 -07: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 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