cranelift-fuzzgen-verify is redundant with cranelift-fuzzgen (#4411)

The compile step that cranelift-fuzzgen does also triggers IR
verification. So all bugs that cranelift-fuzzgen-verify could catch are
also caught by cranelift-fuzzgen. Removing redundant fuzzers lets us
spend limited fuzz-testing CPU time budgets better.

fuzz/Cargo.toml

@@ -96,12 +96,6 @@ doc = false
 # test = false
 # doc = false
 
-# [[bin]]
-# name = "cranelift-fuzzgen-verify"
-# path = "fuzz_targets/cranelift-fuzzgen-verify.rs"
-# test = false
-# doc = false
-
 [[bin]]
 name = "instantiate-many"
 path = "fuzz_targets/instantiate-many.rs"

fuzz/README.md

@@ -30,8 +30,6 @@ At the time of writing, we have the following fuzz targets:
 * `cranelift-fuzzgen`: Generate a Cranelift function and check that it returns
   the same results when compiled to the host and when using the Cranelift
   interpreter; only a subset of Cranelift IR is currently supported.
-* `cranelift-fuzzgen-verify`: Stress the Cranelift IR verifier by generating a
-  Cranelift function and checking that it is indeed a valid function.
 * `differential`: Generate a Wasm module and check that Wasmtime returns
   the same results when run with two different configurations.
 * `differential_spec`: Generate a Wasm module and check that Wasmtime returns

fuzz/fuzz_targets/cranelift-fuzzgen-verify.rs

@@ -1,11 +0,0 @@
-#![no_main]
-
-use libfuzzer_sys::fuzz_target;
-
-use cranelift_codegen::{settings, verify_function};
-use cranelift_fuzzgen::TestCase;
-
-fuzz_target!(|testcase: TestCase| {
-    let flags = settings::Flags::new(settings::builder());
-    verify_function(&testcase.func, &flags).unwrap();
-});