Files
regalloc2/fuzz/Cargo.toml
Jamey Sharp 47cb8234b6 Remove old tests and reexport libfuzzer from fuzzing module (#69)
* Remove unused regalloc2-test crate

This code doesn't build, and Chris says it's "a really old harness that
existed prior to building the fuzzing and was used mainly to profile and
get stats before integration with Cranelift".

* Re-export libfuzzer/arbitrary from fuzzing module

This avoids needing to keep dependencies on `arbitrary` in sync across
the three different Cargo.toml files in this project.

However, before version 0.4.2, libfuzzer-sys only supported using its
macros if it was available at the top-level `libfuzzer_sys` path, which
breaks when re-exporting it. So I'm upgrading to that version (or the
newest patch release of it).

Upgrading libfuzzer-sys in turn brings in the 1.0 release of the
arbitrary crate, with a minor API change along the way.
2022-08-03 14:28:37 -07:00

56 lines
998 B
TOML

[package]
name = "regalloc2-fuzz"
version = "0.0.0"
authors = ["Chris Fallin <chris@cfallin.org>"]
license = "MPL-2.0 AND Apache-2.0 WITH LLVM-exception"
publish = false
edition = "2018"
[package.metadata]
cargo-fuzz = true
[dependencies]
regalloc2 = { path = "../", features = ["fuzzing"] }
log = { version = "0.4.8", default-features = false }
env_logger = "0.8.3"
# Prevent this from interfering with workspaces
[workspace]
members = ["."]
[[bin]]
name = "domtree"
path = "fuzz_targets/domtree.rs"
test = false
doc = false
[[bin]]
name = "ssagen"
path = "fuzz_targets/ssagen.rs"
test = false
doc = false
[[bin]]
name = "ion"
path = "fuzz_targets/ion.rs"
test = false
doc = false
[[bin]]
name = "moves"
path = "fuzz_targets/moves.rs"
test = false
doc = false
[[bin]]
name = "ion_checker"
path = "fuzz_targets/ion_checker.rs"
test = false
doc = false
# Enable debug assertions and overflow checks when fuzzing
[profile.release]
debug = true
debug-assertions = true
overflow-checks = true