We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
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
Historically a lot of the pthread implementation in emscripten was custom JS code.
We have been slowly moving towards using the musl C code where possible and there is still some work to do here. Doing this has several advantages:
Even when we can't use the musl code directly, moving the code to C is from JS has its advantages too.
Some of the work already done: #12861 #14858 #14853 #14775 #14707 #14484 #12839 #12615
The text was updated successfully, but these errors were encountered:
PR #15603 and #15604 are also relevant here. After that, most pthread APIs have been moved to musl (I think).
Another advantage of doing this is that simplifying library_pthread.js becomes easier (see e.g. work-in-progress commit bf592e8).
library_pthread.js
Sorry, something went wrong.
emscripten_futex_wait
I think this is largely done now!
No branches or pull requests
Historically a lot of the pthread implementation in emscripten was custom JS code.
We have been slowly moving towards using the musl C code where possible and there is
still some work to do here. Doing this has several advantages:
Even when we can't use the musl code directly, moving the code to C is from JS
has its advantages too.
Some of the work already done: #12861 #14858 #14853 #14775 #14707 #14484 #12839 #12615
The text was updated successfully, but these errors were encountered: