T0b1/wasmtime
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
Files
d4b771e5a30ff3ec5eb929e7276f1bd6ff87c6d9
wasmtime/crates/fuzzing/wasm-spec-interpreter
History
Alex Crichton 4933762d81 Add release notes for 3.0.1 and update some versions (#5364) 
* Add release notes for 3.0.1

* Update some version directives for crates in Wasmtime

* Mark anything with `publish = false` as version 0.0.0
* Mark the icache coherence crate with the same version as Wasmtime

* Fix manifest directives
2022-12-06 01:26:39 +00:00
..
ocaml
fuzz: improve the spec interpreter (#4881)
2022-09-12 14:23:03 -07:00
src
fuzz: improve the spec interpreter (#4881)
2022-09-12 14:23:03 -07:00
tests
fuzz: improve the spec interpreter (#4881)
2022-09-12 14:23:03 -07:00
build.rs
fuzz: improve the spec interpreter (#4881)
2022-09-12 14:23:03 -07:00
Cargo.toml
Add release notes for 3.0.1 and update some versions (#5364)
2022-12-06 01:26:39 +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