cranelift/fuzz/fuzz_targets/instantiate.rs

#![no_main]

use libfuzzer_sys::fuzz_target;
use wasmtime::Strategy;
use wasmtime_fuzzing::oracles;

fuzz_target!(|data: &[u8]| {
    oracles::instantiate(data, false, Strategy::Auto);
});
Add fuzz targets for module instantiation. 6 years ago			`#![no_main]`

Remove unneeded `extern crate`, `macro_use`, and tidy `use`s. 5 years ago			`use libfuzzer_sys::fuzz_target;`
Remove usage of `CompilationStrategy` from `Config` (#764) * Remove usage of `CompilationStrategy` from `Config` This commit removes the public API usage of the internal `CompilationStrategy` enumeration from the `Config` type in the `wasmtime` crate. To do this the `enum` was copied locally into the crate and renamed `Strategy`. The high-level description of this change is: * The `Config::strategy` method now takes a locally-defined `Strategy` enumeration instead of an internal type. * The contents of `Strategy` are always the same, not relying on Cargo features to indicate which variants are present. This avoids unnecessary downstream `#[cfg]`. * A `lightbeam` feature was added to the `wasmtime` crate itself to lightbeam compilation support. * The `Config::strategy` method is now fallible. It returns a runtime error if support for the selected strategy wasn't compiled in. * The `Strategy` enum is listed as `#[non_exhaustive]` so we can safely add variants over time to it. This reduces the public crate dependencies of the `wasmtime` crate itself, removing the need to reach into internal crates even more! cc #708 * Fix fuzz targets * Update nightly used to build releases * Run rustfmt 5 years ago			`use wasmtime::Strategy;`
Remove always-on logging from fuzz targets (#878) Now that the `cargo fuzz` tooling is better, it is easier to reproduce failures, and we don't need to be super paranoid about logging here. 5 years ago			`use wasmtime_fuzzing::oracles;`
Add fuzz targets for module instantiation. 6 years ago
			`fuzz_target!(\|data: &[u8]\| {`
Fix fuzzer expectation about valid modules Recent changes to fuzzers made expectations more strict about handling errors while fuzzing, but this erroneously changed a module compilation step to always assume that the input wasm is valid. Instead a flag is now passed through indicating whether the wasm blob is known valid or invalid, and only if compilation fails and it's known valid do we panic. 4 years ago			`oracles::instantiate(data, false, Strategy::Auto);`
Add fuzz targets for module instantiation. 6 years ago			`});`