Skip to content

Mention gettid() in Wasm Worker docs. NFC #26754

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.

Sign up for GitHub

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

Merged
sbc100 merged 1 commit into from
Apr 23, 2026
Merged

Mention gettid() in Wasm Worker docs. NFC #26754

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion site/source/docs/api_reference/wasm_workers.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -95,7 +95,8 @@ Pthreads and Wasm Workers share several similarities:
* Both types of threads support TLS via explicitly linked in Wasm globals (see
``test/wasm_worker/wasm_worker_tls_wasm_assembly.c/.S`` for example code)
* Both types of threads have a concept of a thread ID (``pthread_self()`` for pthreads,
``emscripten_wasm_worker_self_id()`` for Wasm Workers)
``emscripten_wasm_worker_self_id()`` for Wasm Workers). `gettid()` works in
both contexts so is more portable.
* Both types of threads can perform an event-based and an infinite loop programming model.
* Both can use ``EM_ASM`` and ``EM_JS`` API to execute JS code on the calling thread.
* Both can call out to JS library functions (linked in with ``--js-library`` directive) to
Expand Down
Loading