binaryen's ttf and wasm-smith · wasmtime

Stream: wasmtime

Topic: binaryen's ttf and wasm-smith

Alex Crichton (Oct 28 2020 at 19:44):

@fitzgen (he/him) do you think we should keep binaryen's -ttf generation for fuzzing? I think it's good to have multiple fuzzers but the downsides right now are that binaryen-sys is largely unmaintained (we can probably ping pepyakin for a publish but all the maintenance would be on us for a crate we don't own) so we're not picking up any new bugfixes or anything like that, and there's a number of fuzz bugs which are timing out in binaryen's generation of the module itself

Alex Crichton (Oct 28 2020 at 19:44):

we could always investigate binaryen, debug it, fix it, and make PRs, but it's a lot of work to do that relative to wasm-smith now

Alex Crichton (Oct 28 2020 at 19:45):

This is basically https://github.com/bytecodealliance/wasmtime/issues/2163, but we've got 4-5 fuzz bugs I think now related to binaryen, and I'm not overly thrilled about investigating all of them

Investigate slow fuzz module generation with binaryen · Issue #2163 · bytecodealliance/wasmtime

One of our fuzz bugs on OSS-Fuzz is that we're timing out when running the equivalent of wasm-opt -ttf. This timeout means that we don't even start executing wasmtime to compile/instantiate...

fitzgen (he/him) (Oct 28 2020 at 19:53):

Yeah I think we can probably drop binaryen

Alex Crichton (Oct 28 2020 at 20:26):

ok I'll whip up a PR

Last updated: Dec 23 2024 at 13:07 UTC