-
Notifications
You must be signed in to change notification settings - Fork 1.2k
[wasm] Use pthread API for NSLock for wasip1-threads target #5293
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
kateinoigakukun
wants to merge
2
commits into
swiftlang:main
Choose a base branch
from
kateinoigakukun:pr-f8de02d185c8183f6a63950b75731c051be41c42
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
[wasm] Use pthread API for NSLock for wasip1-threads target #5293
kateinoigakukun
wants to merge
2
commits into
swiftlang:main
from
kateinoigakukun:pr-f8de02d185c8183f6a63950b75731c051be41c42
Conversation
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
`SWIFT_CORELIBS_FOUNDATION_HAS_THREADS` is not defined for all WASI targets now but we do have pthread support for wasip1-threads target. `_runtime(_multithreaded)` check is more appropriate here to detect multithreaded runtime support. We can remove `SWIFT_CORELIBS_FOUNDATION_HAS_THREADS` definition later.
Member
Author
|
@swift-ci test |
Recent wasi-libc versions include pthreads support for wasip1-threads target and a stub implementation for wasip1 target.
a46f221 to
30ec87a
Compare
Member
Author
|
@swift-ci test |
1 similar comment
Member
Author
|
@swift-ci test |
compnerd
reviewed
Dec 12, 2025
Member
compnerd
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is SWIFT_CORELIBS_FOUNDATION_HAS_THREADS used at all anymore? I wonder if we should drop the flag now.
Member
Author
|
@compnerd Yes, that change is already on my working branch and will be the next PR after this PR get merged |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
SWIFT_CORELIBS_FOUNDATION_HAS_THREADSis not defined for all WASI targets now but we do have pthread support for wasip1-threads target._runtime(_multithreaded)check is more appropriate here to detect multithreaded runtime support. We can removeSWIFT_CORELIBS_FOUNDATION_HAS_THREADSdefinition later.