[WIP] Generate memory.atomic.wait with a 0 timeout in fuzzer - #9170
Draft
stevenfontanella wants to merge 1 commit into
Draft
stevenfontanella wants to merge 1 commit into
stevenfontanella wants to merge 1 commit into
Conversation
stevenfontanella
force-pushed
the
atomicwait
branch
from
September 29, 2026 18:20
1441126 to
6a93cb9
Compare
stevenfontanella
force-pushed
the
atomicwait
branch
from
September 29, 2026 20:32
6a93cb9 to
ea261c4
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Followup to #9012 to make
memory.atomic.waitmore similar tostruct.wait. Probably fixes #8429, although we don't have a way to verify.Previously we never attempted to generate
memory.atomic.wait. In addition, if our seed file (e.g. from an existing test case) happened to containmemory.atomic.wait, we had no guarantee that the resulting binary wouldn't hang forever due to not being notified and having a timeout of -1 or excessively long.Change the fuzzer to instead generate
memory.atomic.wait, but force its timeout param to always be 0 when!ATOMIC_WAITS.