aboutsummaryrefslogtreecommitdiff
path: root/test/cases/compile_errors/setAlignStack_in_inline_function.zig
diff options
context:
space:
mode:
authorLucas Santos <lucascarvalhosantos91@gmail.com>2025-12-25 22:08:34 -0300
committerAndrew Kelley <andrewrk@noreply.codeberg.org>2025-12-27 20:40:19 +0100
commitef77cc0de1f4453d89d8841116eaa65a42a9c89f (patch)
tree02246336362aa127cf6c4ec806c6f38f0dc11fd4 /test/cases/compile_errors/setAlignStack_in_inline_function.zig
parent9db3e23e8081e7598e35a2da53a2b29c064d8404 (diff)
downloadzig-ef77cc0de1f4453d89d8841116eaa65a42a9c89f.tar.gz
zig-ef77cc0de1f4453d89d8841116eaa65a42a9c89f.zip
Fixes doc comment of Futex.wait
On Windows, changing the value at the target address is not sufficient, there needs to be a wake call. From [MSDN](https://learn.microsoft.com/en-us/windows/win32/api/synchapi/nf-synchapi-waitonaddress): > If the value at Address differs from the value at CompareAddress, the function returns immediately. If the values are the same, the function does not return until another thread in the same process signals that the value at Address has changed by calling WakeByAddressSingle or WakeByAddressAll or the timeout elapses, whichever comes first. We could note that this behavior is only observed on Windows. However, if we want the function to have consistent behavior across all platforms, we should require users to call wake. On platforms where changing the value is sufficient to wake the waiting thread, an unblocking of the thread without a matching wake would just be considered a spurious wake.
Diffstat (limited to 'test/cases/compile_errors/setAlignStack_in_inline_function.zig')
0 files changed, 0 insertions, 0 deletions