Skip to content
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

Stop bothering WASI apps including unimplemented syscalls #415

Merged
merged 2 commits into from
Jan 16, 2024

Conversation

kateinoigakukun
Copy link
Member

@kateinoigakukun kateinoigakukun commented Jan 16, 2024

The recent wasi-libc includes some new syscalls not implemented in
@wasmer-js/wasi and we currently disable --gc-sections (see
swiftwasm/swift#5128), so binaries built with
SwiftWasm 5.9 toolchain contains references to those unimplemented
syscalls.
This commit allows running such binaries by inserting dummy functions
for unimplemented syscalls.

The recent wasi-libc includes some new syscalls not implemented in
@wasmer-js/wasi and we currently disable `--gc-sections` (see
swiftwasm/swift#5128), so binaries built with
SwiftWasm 5.9 toolchain contains references to those unimplemented
syscalls.
This commit allows running such binaries by inserting dummy functions
for unimplemented syscalls.
@kateinoigakukun kateinoigakukun added the bug Something isn't working label Jan 16, 2024
@kateinoigakukun kateinoigakukun requested a review from a team January 16, 2024 13:02
@kateinoigakukun
Copy link
Member Author

Thanks!

@kateinoigakukun kateinoigakukun merged commit ac49166 into main Jan 16, 2024
5 of 6 checks passed
@kateinoigakukun kateinoigakukun deleted the yt/new-wasi-syscalls branch January 16, 2024 13:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants