Wasmtime GitHub notifications bot (Nov 21 2025 at 16:08): Wasmtime GitHub notifications bot (Nov 21 2025 at 16:08):alexcrichton opened issue #12067:
Currently wasm-smith doesn't generate any atomic instructions at all, meaning there's no fuzz coverage of atomics. Before re-enabling threads as tier 1 we should ensure that this is taken care of.
Wasmtime GitHub notifications bot (Nov 21 2025 at 16:08):alexcrichton added the fuzzing label to Issue #12067.
Wasmtime GitHub notifications bot (Nov 21 2025 at 16:08):alexcrichton added the wasm-proposal:threads label to Issue #12067.
Wasmtime GitHub notifications bot (Nov 21 2025 at 16:09):github-actions[bot] commented on issue #12067:
Subscribe to Label Action
cc @fitzgen
<details>
This issue or pull request has been labeled: "fuzzing"Thus the following users have been cc'd because of the following labels:
- fitzgen: fuzzing
To subscribe or unsubscribe from this label, edit the <code>.github/subscribe-to-label.json</code> configuration file.
Learn more.
</details>
Wasmtime GitHub notifications bot (Nov 21 2025 at 18:44):fitzgen commented on issue #12067:
Filed an upstream issue for adding this support to
wasm-smith: https://github.com/bytecodealliance/wasm-tools/issues/2384
Wasmtime GitHub notifications bot (Nov 30 2025 at 18:07):danielvallance commented on issue #12067:
should this be closed now that https://github.com/bytecodealliance/wasm-tools/pull/2386 has been merged ?
Wasmtime GitHub notifications bot (Dec 01 2025 at 16:41):alexcrichton commented on issue #12067:
Not quite unfortunately. Fuzzing of threads was disabled in https://github.com/bytecodealliance/wasmtime/pull/12036 and even with an update to wasm-tools Wasmtime still won't be fuzzing these instructions. Fuzzing currently can't happen due to
ResourceLimiternot applying to shared memories, and that'll need to get fixed to turn this back on.
Last updated: Dec 06 2025 at 07:03 UTC