rust jit wasm webassembly runtime wasi cranelift sandbox wasmtime

History

Alex Crichton 5856590fae Configure workspace lints, enable running some Clippy lints on CI (#7561 ) * Configure Rust lints at the workspace level This commit adds necessary configuration knobs to have lints configured at the workspace level in Wasmtime rather than the crate level. This uses a feature of Cargo first released with 1.74.0 (last week) of the `[workspace.lints]` table. This should help create a more consistent set of lints applied across all crates in our workspace in addition to possibly running select clippy lints on CI as well. * Move `unused_extern_crates` to the workspace level This commit configures a `deny` lint level for the `unused_extern_crates` lint to the workspace level rather than the previous configuration at the individual crate level. * Move `trivial_numeric_casts` to workspace level * Change workspace lint levels to `warn` CI will ensure that these don't get checked into the codebase and otherwise provide fewer speed bumps for in-process development. * Move `unstable_features` lint to workspace level * Move `unused_import_braces` lint to workspace level * Start running Clippy on CI This commit configures our CI to run `cargo clippy --workspace` for all merged PRs. Historically this hasn't been all the feasible due to the amount of configuration required to control the number of warnings on CI, but with Cargo's new `[lint]` table it's possible to have a one-liner to silence all lints from Clippy by default. This commit by default sets the `all` lint in Clippy to `allow` to by-default disable warnings from Clippy. The goal of this PR is to enable selective access to Clippy lints for Wasmtime on CI. * Selectively enable `clippy::cast_sign_loss` This would have fixed #7558 so try to head off future issues with that by warning against this situation in a few crates. This lint is still quite noisy though for Cranelift for example so it's not worthwhile at this time to enable it for the whole workspace. * Fix CI error prtest:full		12 months ago
..
ocaml	fuzz: improve the spec interpreter (#4881)	2 years ago
src	fuzz: improve the spec interpreter (#4881)	2 years ago
tests	fuzz: improve the spec interpreter (#4881)	2 years ago
Cargo.toml	Configure workspace lints, enable running some Clippy lints on CI (#7561)	12 months ago
README.md	fuzz: improve wasm-spec-interpreter documentation, add library path (#4007)	3 years ago
build.rs	fuzz: improve the spec interpreter (#4881)	2 years ago

README.md

wasm-spec-interpreter

This project shows how to use ocaml-interop to call into the Wasm spec interpreter. There are several steps to making this work:

building the OCaml Wasm spec interpreter as a static library
building a Rust-to-OCaml FFI bridge using ocaml-interop and a custom OCaml wrapper
linking both things into a Rust crate

Dependencies

This crate only builds in an environment with:

make (the Wasm spec interpreter uses a Makefile)
ocamlopt, ocamlbuild (available with, e.g., dnf install ocaml)
Linux tools (e.g. ar); currently it is easiest to build the static libraries in a single environment but this could be fixed in the future (TODO)
libgmp, for the OCaml zarith package
git is used by build.rs to retrieve the repository containing the Wasm spec interpreter; it is safe to completely remove ocaml/spec to get a new copy

Build

cargo build --features build-libinterpret

Use FFI_LIB_DIR=path/to/lib/... to specify a different location for the static library (this is mainly for debugging). If the build-libinterpret feature is not provided, this crate will build successfully but fail at runtime.

Test

cargo test --features build-libinterpret