threads: implement support for unnamed semaphores#316
Merged
abrown merged 2 commits intoWebAssembly:mainfrom Aug 22, 2022
Merged
threads: implement support for unnamed semaphores#316abrown merged 2 commits intoWebAssembly:mainfrom
abrown merged 2 commits intoWebAssembly:mainfrom
Conversation
abrown
force-pushed
the
pthreads-semaphore
branch
from
00b9418 to
6eccb77
Compare
[POSIX semaphores] come in two forms: named and unnamed. Roughly, named semaphores use files to implement locking across processes; unnamed semaphores use a shared memory region to implement locking across threads in the same process. Since WASI currently has no process concept (and it is relatively unclear how to map the WASI files as shared memory), only the unnamed semaphores are supported by this changed. This means that `sem_open`, `sem_close`, and `sem_unlink` will not available to programs compiled with a threads-enabled `wasi-libc`. [POSIX semaphores]: https://man7.org/linux/man-pages/man7/sem_overview.7.html
abrown
force-pushed
the
pthreads-semaphore
branch
from
6eccb77 to
b8d0356
Compare
sbc100
approved these changes
Aug 22, 2022
john-sharratt
pushed a commit
to john-sharratt/wasix-libc
that referenced
this pull request
Mar 6, 2023
[POSIX semaphores] come in two forms: named and unnamed. Roughly, named semaphores use files to implement locking across processes; unnamed semaphores use a shared memory region to implement locking across threads in the same process. Since WASI currently has no process concept (and it is relatively unclear how to map the WASI files as shared memory), only the unnamed semaphores are supported by this changed. This means that `sem_open`, `sem_close`, and `sem_unlink` will not available to programs compiled with a threads-enabled `wasi-libc`. [POSIX semaphores]: https://man7.org/linux/man-pages/man7/sem_overview.7.html
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.
POSIX semaphores come in two forms: named and unnamed. Roughly, named
semaphores use files to implement locking across processes; unnamed
semaphores use a shared memory region to implement locking across
threads in the same process. Since WASI currently has no process concept
(and it is relatively unclear how to map the WASI files as shared
memory), only the unnamed semaphores are supported by this changed. This
means that
sem_open,sem_close, andsem_unlinkwill not availableto programs compiled with a threads-enabled
wasi-libc.