-
Notifications
You must be signed in to change notification settings - Fork 258
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
remove __wasi_proc_raise() #7
Labels
proposal
A discussion about a specific actionable item
Comments
|
yamt
added a commit
to yamt/wasm-micro-runtime
that referenced
this issue
Apr 27, 2022
…lable Many of these signal constants are not available on NuttX. Maybe we can remove these signal stuff sooner or later. WebAssembly/WASI#7 WebAssembly/wasi-libc#278
wenyongh
pushed a commit
to bytecodealliance/wasm-micro-runtime
that referenced
this issue
Apr 27, 2022
…lable (#1125) Many of these signal constants are not available on NuttX. Maybe we can remove these signal stuff sooner or later: WebAssembly/WASI#7 WebAssembly/wasi-libc#278
victoryang00
pushed a commit
to victoryang00/wamr-aot-gc-checkpoint-restore
that referenced
this issue
May 27, 2024
…lable (bytecodealliance#1125) Many of these signal constants are not available on NuttX. Maybe we can remove these signal stuff sooner or later: WebAssembly/WASI#7 WebAssembly/wasi-libc#278
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
From bytecodealliance/wasmtime#68:
__wasi_proc_raise in its current form is effectively just a variant of __wasi_proc_exit which produces an exit status indicating that the process was killed with a signal rather than exiting normally.
I agree that this is obscure, and it could create complications if real signal handling is added later, so we should consider removing it.
The text was updated successfully, but these errors were encountered: