Files

Alex Crichton 174b60dcf7 Add *.wast support for invoking components (#4526 )

This commit builds on bytecodealliance/wasm-tools#690 to add support to
testing of the component model to execute functions when running
`*.wast` files. This support is all built on #4442 as functions are
invoked through a "dynamic" API. Right now the testing and integration
is fairly crude but I'm hoping that we can try to improve it over time
as necessary. For now this should provide a hopefully more convenient
syntax for unit tests and the like.

2022-07-27 21:02:16 +00:00

ocaml

enable multi-value in spec intepreter fuzzing (#4118 )

2022-05-10 10:33:07 -05:00

src

Migrate most of wasmtime from lazy_static to once_cell (#4368 )

2022-07-05 10:52:48 -07:00

tests

support SIMD fuzzing in reference interpreter (#3980 )

2022-03-31 10:07:39 -05:00

build.rs

enable multi-value in spec intepreter fuzzing (#4118 )

2022-05-10 10:33:07 -05:00

Cargo.toml

Add *.wast support for invoking components (#4526 )

2022-07-27 21:02:16 +00:00

README.md

fuzz: improve wasm-spec-interpreter documentation, add library path (#4007 )

2022-04-11 09:07:58 -05:00

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