Files

Alex Crichton 8aad99ffae Fix allowing an override of LIBGMP_PATHS (#3870 )

This seems to have intended to allow overrides but the specific Makefile
syntax used didn't actually allow overrides, so update that to allow env
vars from the outside world to override the variable (needed locally on
AArch64 I'm building on which has a different path to libgmp)

2022-03-02 11:41:59 -06:00

ocaml

Fix allowing an override of LIBGMP_PATHS (#3870 )

2022-03-02 11:41:59 -06:00

src

Fuzzing against verified fork of spec interpreter (#3843 )

2022-03-01 12:01:46 -06:00

tests

Fuzzing against verified fork of spec interpreter (#3843 )

2022-03-01 12:01:46 -06:00

build.rs

Pin spec interpreter to a specific revision (#3868 )

2022-03-02 10:54:05 -06:00

Cargo.toml

Add a crate to interface with the WebAssembly spec interpreter

2021-08-10 11:56:07 -07:00

README.md

Add a crate to interface with the WebAssembly spec interpreter

2021-08-10 11:56:07 -07: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)

Remember to retrieve the Wasm spec submodule:

git clone ... --recursive

Build

RUSTFLAGS=--cfg=fuzzing cargo build

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

Test

RUSTFLAGS=--cfg=fuzzing cargo test