summaryrefslogtreecommitdiff
path: root/test/lit/exec
diff options
context:
space:
mode:
authorThomas Lively <tlively@google.com>2024-03-29 13:12:42 -0700
committerGitHub <noreply@github.com>2024-03-29 13:12:42 -0700
commit08a18cdaf95bcf46df851d15d09bfc3737f3fe2b (patch)
tree18010dad170d8b3890047292de3e98827a023a1d /test/lit/exec
parentb10d59d1d201506eba1aaba035e699fec849ea60 (diff)
downloadbinaryen-08a18cdaf95bcf46df851d15d09bfc3737f3fe2b.tar.gz
binaryen-08a18cdaf95bcf46df851d15d09bfc3737f3fe2b.tar.bz2
binaryen-08a18cdaf95bcf46df851d15d09bfc3737f3fe2b.zip
Report timeout in interpretation of AtomicWait (#6452)
To avoid slow-running fuzz cases, we report a host limit when interpreting atomic.wait with any non-zero timeout. However, in the allowed case where the timeout is zero, we were incorrectly interpreting the wait as returning 0, meaning that it was woken up, instead of 2, meaning that the timeout expired. Fix it to return 2.
Diffstat (limited to 'test/lit/exec')
-rw-r--r--test/lit/exec/atomic.wast2
1 files changed, 1 insertions, 1 deletions
diff --git a/test/lit/exec/atomic.wast b/test/lit/exec/atomic.wast
index 73567121f..631bdd531 100644
--- a/test/lit/exec/atomic.wast
+++ b/test/lit/exec/atomic.wast
@@ -8,7 +8,7 @@
(memory $0 23 256 shared)
;; CHECK: [fuzz-exec] calling wait_and_log
- ;; CHECK-NEXT: [LoggingExternalInterface logging 0]
+ ;; CHECK-NEXT: [LoggingExternalInterface logging 2]
(func $wait_and_log (export "wait_and_log")
(call $log
(memory.atomic.wait64