alexcrichton commented on issue #4410:
I might instead recommend following a similar pattern we have for fuzzing wasmtime where
log-levels are used to control this and, when enabled, it jettisons a file out the side to be read later. In Wasmtime we emit both*.{wasm,wat}for convenience but here it could presumably emit*.clifperhaps?
afonso360 commented on issue #4410:
Does
cargo fuzz fmt cranelift-fuzzgen-verify <input>cover this use case?According to the docs it prints a std::fmt::Debug for the input, which should have the function.
jameysharp commented on issue #4410:
I didn't see
cargo fuzz fmtdespite looking for all the options I could find, and yes, that does exactly what I wanted. Thanks!
Last updated: Dec 06 2025 at 06:05 UTC