From 08a18cdaf95bcf46df851d15d09bfc3737f3fe2b Mon Sep 17 00:00:00 2001 From: Thomas Lively Date: Fri, 29 Mar 2024 13:12:42 -0700 Subject: 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. --- test/lit/exec/atomic.wast | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'test/lit/exec') 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 -- cgit v1.2.3