Wasmtime GitHub notifications bot (Dec 06 2022 at 20:00): Wasmtime GitHub notifications bot (Dec 06 2022 at 20:00):jameysharp commented on issue #2498:
It looks like the
WatGeneratorwas deleted in #3958. Did we lose some useful fuzzing functionality at that point? If so, maybe we should revive this issue. If the dummy generator doesn't need this level of complexity though, I guess we should close this issue as well as #2535.
Wasmtime GitHub notifications bot (Sep 24 2025 at 15:20):bjorn3 commented on issue #2498:
What is the status of this issue?
Wasmtime GitHub notifications bot (Sep 29 2025 at 18:24):fitzgen closed issue #2498:
In https://github.com/bytecodealliance/wasmtime/pull/2497#discussion_r541118846 we added support for generating nested modules, and we generate these modules by concatenating strings of WAT and then passing it to
Module::newwhich internally checks for WAT strings and assembles them into Wasm bytes if necessary.We can make this more efficient, improving the number of test cases we fuzz in a given amount of time, by generating Wasm bytes directly via the
wasm-encodercrate, rather than generating a WAT string. Thewasm-encodercrate has builder methods that should make it pretty straightforward to translate theWatGeneratorinto aWasmGenerator.If you want to work on this issue, leave a comment, and let me know whatever questions you have!
Info for getting up and running with contributing: https://docs.wasmtime.dev/contributing.html
Last updated: Dec 13 2025 at 19:03 UTC