-
-
Notifications
You must be signed in to change notification settings - Fork 33.7k
gh-124621: Emscripten: Add support for async input devices #136822
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
Merged
Merged
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
Contributor
Author
|
!buildbot emscripten |
|
🤖 New build scheduled with the buildbot fleet by @hoodmane for commit 3d573d5 🤖 Results will be shown at: https://buildbot.python.org/all/#/grid?branch=refs%2Fpull%2F136822%2Fmerge The command will test the builders whose names match following regular expression: The builders matched are:
|
This is useful for implementing proper `input()`. It requires the JavaScript engine to support the wasm JSPI spec which is now stage 4. It is supported on Chrome since version 137 and on Firefox and node behind a flag. We override the `__wasi_fd_read()` syscall with our own variant that checks for a readAsync operation. If it has it, we use our own async variant of `fd_read()`, otherwise we use the original `fd_read()`. We also add a variant of `FS.createDevice()` called `FS.createAsyncInputDevice()`. Finally, if JSPI is available, we wrap the `main()` symbol with `WebAssembly.promising()` so that we can stack switch from `fd_read()`. If JSPI is not available, attempting to read from an AsyncInputDevice will raise an `OSError`.
3d573d5 to
7d0e709
Compare
This is useful for implementing proper
input(). It requires the JavaScript engine to support the wasm JSPI spec which is now stage 4. It is supported on Chrome since version 137 and on Firefox and node behind a flag.We override the
__wasi_fd_read()syscall with our own variant that checks for a readAsync operation. If it has it, we use our own async variant offd_read(), otherwise we use the originalfd_read(). We also add a variant ofFS.createDevice()calledFS.createAsyncInputDevice().Finally, if JSPI is available, we wrap the
main()symbol withWebAssembly.promising()so that we can stack switch fromfd_read(). If JSPI is not available, attempting to read from an AsyncInputDevice will raise anOSError.