Implement sem_timedwait - #80
Open
pnewell wants to merge 2 commits into
Open
Conversation
- Include 0 in some so behavior matches other platforms - Set timeout value to u.some when value is 0 or greater
- __futex4_cp is implemented and __wasilibc_futex_wait_wasix is now working properly, so removing fallback infinite wait
Arshia001
self-requested a review
August 12, 2025 11:37
|
Hey @pnewell, thanks for this contribution! Can you please share a code snippet that was broken before this change, but now works correctly? |
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
2 participants
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.
sem_timedwait relies on __timedwait_cp which is currently using a fallback that ignores the passed in value.
This branch: