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

Initial wasi/wasm support for fs, uio, zerocopy #2011

Closed
wants to merge 4 commits into from

Conversation

connor4312
Copy link

@connor4312 connor4312 commented Mar 7, 2023

References #786
Depends on rust-lang/libc#3143, hence marking as a draft. Done

This implements WASI support sufficient to build the fs, uio, and zerocopy features (enough to build coreutils 🙂)

Lots of stuff is flagged out since file permissions aren't present in wasi_snapshot_preview1 which is what rust supports out of the box for wasm32-wasi.

One kind of weird thing is dealing with PATH_MAX. WASI doesn't define one, it's whatever the host system is, but afaik there's not an API to get this. So for WASI I defaulted to libc's "linux_like" value of 4096. Let me know what you think.

Cargo.toml Outdated Show resolved Hide resolved
Cargo.toml Outdated Show resolved Hide resolved
@connor4312 connor4312 marked this pull request as draft March 7, 2023 23:05
@connor4312 connor4312 marked this pull request as ready for review March 8, 2023 17:00
@connor4312 connor4312 force-pushed the master branch 2 times, most recently from c678a4a to 8cf83f3 Compare March 8, 2023 22:23
@connor4312
Copy link
Author

Looks like build failure is a flake

@atilag
Copy link

atilag commented Sep 11, 2023

I guess these changes could also be applied to target="emscripten", am I right?
Just asking because I'm targeting this platform :)

@connor4312 connor4312 closed this Oct 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants