This repository has been archived by the owner on Mar 24, 2022. It is now read-only.
Add differential fuzzing between old and new Cranelift backends. #617
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds a fuzz target runnable via
cargo-fuzz
(withlibFuzzer
)that builds an arbitrary Wasm module, produced by
wasm-smith
, withlucetc
using both the old and new Cranelift x86-64 backends. It theninstantiates both and invokes the start function in both, comparing the
global values and heap contents after the call returns.
The intent of this differential fuzzing is to validate that the new
backend works as well as the old one for the purposes of Lucet.
This change pulls in a new version of wasmtime and fixes a few small
issues (panics that should be errors) that the fuzzing immediately
discovered.