cranelift/fuzz/Cargo.toml

[package]
name = "wasmtime-fuzz"
version = "0.12.0"
authors = ["The Wasmtime Project Developers"]
edition = "2018"
publish = false

[package.metadata]
cargo-fuzz = true

[dependencies]
arbitrary = "0.2.0"
wasmtime-fuzzing = { path = "../crates/fuzzing" }
wasmtime = { path = "../crates/api" }
libfuzzer-sys = "0.2.1"

[[bin]]
name = "compile"
path = "fuzz_targets/compile.rs"
test = false
doc = false

[[bin]]
name = "instantiate"
path = "fuzz_targets/instantiate.rs"
test = false
doc = false

[[bin]]
name = "instantiate_translated"
path = "fuzz_targets/instantiate_translated.rs"
test = false
doc = false

[[bin]]
name = "api_calls"
path = "fuzz_targets/api_calls.rs"
test = false
doc = false

[[bin]]
name = "differential"
path = "fuzz_targets/differential.rs"
test = false
doc = false
Start experimenting with cargo fuzz. This isn't very usable yet. 7 years ago			`[package]`
Make package names consistent with cranelift's. 6 years ago			`name = "wasmtime-fuzz"`
Bump to 0.12.0 (#997) * Bump to 0.12.0 * Another lockfile update 5 years ago			`version = "0.12.0"`
Update Cargo.toml authors fields. 6 years ago			`authors = ["The Wasmtime Project Developers"]`
Update to Rust 2018 Edition. 6 years ago			`edition = "2018"`
Start experimenting with cargo fuzz. This isn't very usable yet. 7 years ago			`publish = false`

			`[package.metadata]`
			`cargo-fuzz = true`

Make package names consistent with cranelift's. 6 years ago			`[dependencies]`
Split our existing fuzz targets into separate generators and oracles Part of #611 5 years ago			`arbitrary = "0.2.0"`
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			`wasmtime-fuzzing = { path = "../crates/fuzzing" }`
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			`wasmtime = { path = "../crates/api" }`
Update libfuzzer-sys dependency version number To support oss-fuzz PoC, see https://github.com/bytecodealliance/wasmtime/issues/611 5 years ago			`libfuzzer-sys = "0.2.1"`
Update to wasmparser 0.22. 6 years ago
Start experimenting with cargo fuzz. This isn't very usable yet. 7 years ago			`[[bin]]`
			`name = "compile"`
			`path = "fuzz_targets/compile.rs"`
Move the `fuzz` directory into main workspace This'll help us track dependencies and head off issues like #721 5 years ago			`test = false`
Tweak some API doc generation (#772) * Build docs with the nightly toolchain so [foo::bar] links work by default. This is a relatively new feature of rustdoc and I thought it was stabilized at this point but apparently it's not! * Tweak some API docs on `wasmtime::Strategy` * Use `--all` to build all local crate documentation instead of trying to list the number of local crates * Tweak some documentation configuration to avoid warnings generated by Cargo. 5 years ago			`doc = false`
Add fuzz targets for module instantiation. 6 years ago
			`[[bin]]`
			`name = "instantiate"`
			`path = "fuzz_targets/instantiate.rs"`
Move the `fuzz` directory into main workspace This'll help us track dependencies and head off issues like #721 5 years ago			`test = false`
Tweak some API doc generation (#772) * Build docs with the nightly toolchain so [foo::bar] links work by default. This is a relatively new feature of rustdoc and I thought it was stabilized at this point but apparently it's not! * Tweak some API docs on `wasmtime::Strategy` * Use `--all` to build all local crate documentation instead of trying to list the number of local crates * Tweak some documentation configuration to avoid warnings generated by Cargo. 5 years ago			`doc = false`
Add fuzz targets for module instantiation. 6 years ago
			`[[bin]]`
			`name = "instantiate_translated"`
			`path = "fuzz_targets/instantiate_translated.rs"`
Move the `fuzz` directory into main workspace This'll help us track dependencies and head off issues like #721 5 years ago			`test = false`
Tweak some API doc generation (#772) * Build docs with the nightly toolchain so [foo::bar] links work by default. This is a relatively new feature of rustdoc and I thought it was stabilized at this point but apparently it's not! * Tweak some API docs on `wasmtime::Strategy` * Use `--all` to build all local crate documentation instead of trying to list the number of local crates * Tweak some documentation configuration to avoid warnings generated by Cargo. 5 years ago			`doc = false`
fuzzing: Add initial API call fuzzer We only generate valid sequences of API calls. To do this, we keep track of what objects we've already created in earlier API calls via the `Scope` struct. To generate even-more-pathological sequences of API calls, we use [swarm testing]: > In swarm testing, the usual practice of potentially including all features > in every test case is abandoned. Rather, a large “swarm” of randomly > generated configurations, each of which omits some features, is used, with > configurations receiving equal resources. [swarm testing]: https://www.cs.utah.edu/~regehr/papers/swarm12.pdf There are more public APIs and instance introspection APIs that we have than this fuzzer exercises right now. We will need a better generator of valid Wasm than `wasm-opt -ttf` to really get the most out of those currently-unexercised APIs, since the Wasm modules generated by `wasm-opt -ttf` don't import and export a huge variety of things. 5 years ago
			`[[bin]]`
			`name = "api_calls"`
			`path = "fuzz_targets/api_calls.rs"`
Move the `fuzz` directory into main workspace This'll help us track dependencies and head off issues like #721 5 years ago			`test = false`
Tweak some API doc generation (#772) * Build docs with the nightly toolchain so [foo::bar] links work by default. This is a relatively new feature of rustdoc and I thought it was stabilized at this point but apparently it's not! * Tweak some API docs on `wasmtime::Strategy` * Use `--all` to build all local crate documentation instead of trying to list the number of local crates * Tweak some documentation configuration to avoid warnings generated by Cargo. 5 years ago			`doc = false`
Add initial differential fuzzing Part of #611 5 years ago
			`[[bin]]`
			`name = "differential"`
			`path = "fuzz_targets/differential.rs"`
fuzz: Don't run tests or docs for `differential` fuzz target 5 years ago			`test = false`
			`doc = false`