bytecodealliance
Atomic instructions are not fuzzed
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.
Subscribe to Label Action
cc @fitzgen
Thus the following users have been cc'd because of the following labels:
- fitzgen: fuzzing
To subscribe or unsubscribe from this label, edit the .github/subscribe-to-label.json configuration file.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
Filed an upstream issue for adding this support to wasm-smith: https://github.com/bytecodealliance/wasm-tools/issues/2384
should this be closed now that https://github.com/bytecodealliance/wasm-tools/pull/2386 has been merged ?
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 ResourceLimiter not applying to shared memories, and that'll need to get fixed to turn this back on.