-
-
Notifications
You must be signed in to change notification settings - Fork 33.1k
[3.14] gh-124621: Emscripten: Add support for async input devices (GH-136822) #136935
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
Conversation
…honGH-136822) 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`. (cherry picked from commit 7ae4749) Co-authored-by: Hood Chatham <[email protected]>
!buildbot emscripten |
🤖 New build scheduled with the buildbot fleet by @hoodmane for commit c93d6a0 🤖 Results will be shown at: https://buildbot.python.org/all/#/grid?branch=refs%2Fpull%2F136935%2Fmerge The command will test the builders whose names match following regular expression: The builders matched are:
|
Yeah |
!buildbot emscripten |
🤖 New build scheduled with the buildbot fleet by @hoodmane for commit 4d7d507 🤖 Results will be shown at: https://buildbot.python.org/all/#/grid?branch=refs%2Fpull%2F136935%2Fmerge The command will test the builders whose names match following regular expression: The builders matched are:
|
…es (pythonGH-136822) (pythonGH-136935) 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`. (cherry picked from commit 7ae4749) Co-authored-by: Hood Chatham <[email protected]>
This is useful for implementing proper
input()
. It requires theJavaScript 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 thatchecks for a readAsync operation. If it has it, we use our own async
variant of
fd_read()
, otherwise we use the originalfd_read()
.We also add a variant of
FS.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 an
OSError
.(cherry picked from commit 7ae4749)
Co-authored-by: Hood Chatham [email protected]