-
Notifications
You must be signed in to change notification settings - Fork 271
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
What module will _start, args, env, and pre-opens be defined in? #508
Comments
It seems maybe it is this, but looks abandoned? e.g. it isn't defined in the new format and untouched recently cc @sunfishcode https://github.com/WebAssembly/wasi-classic-command/blob/main/standard/classic-command/docs.md |
I'm also curious because I was thinking of replacing the C backend of W2C2 or WAsm2C with calls to LibGCCJIT for more parallel building without the need for back-to-back source generation and immediate reparsing. |
Does #509 relate to or answer this question? |
@SamuraiCrow it relates, though it is indirect. For example a "command function" would indeed read things like pre-opens, but pre-opens themselves currently are functions (stat and name). It is still murky to me how this stitches together, particularly how you map snapshot01 to this. I'll try to follow along and thanks for the hint. |
The preview1 #509 is for preview2, which is expected to have an entrypoint function that has arguments for command-line arguments and environment variables. |
I also filed #510 which hopefully makes the preview1 docs a little easier to navigate. It removes the old "phases", "snapshot", and "ephemeral" terminology, and just calls things "preview0" and "preview1", which are the terminology we tend to refer to them by now. |
I noticed here, several wasi modules being clarified. However, it seems there's not enough defined to actually bootstrap a wasi command. Notably, we're missing definition of the _start function, memory (basically nothing works without it), how to enumerate pre-opens and how to get args and env. Are you thinking a "wasi-bootstrap" all in, or micro modules like wasi-env?
The text was updated successfully, but these errors were encountered: