-
Notifications
You must be signed in to change notification settings - Fork 261
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
Confusion about WASI's function types. #495
Comments
this is to do with the actual abi that represents those arguments. the four args are (fd, iovs base pointer, iovs length, bytes written pointer) and the return value is the errno. |
Thanks, but where can I get these ABI informations? |
@abc767234318 the closest I found is: But how ciovec_array is laid out isn't explained anywhere that I can find, as ciovec_array link points to something w/ just size and alignment, and no description of how a List is laid out. |
What should I do if I want to pass the Do I have to write a loop to copy to linear memory first? Is there a more efficient way of passing it? |
In addition, the type of WASI/legacy/preview1/witx/typenames.witx Line 284 in a7be582
but it seems there are no document that specified how this "handle" value for $fd should be written for example in .wat file.
I found some sentences in another WebAssembly repository that describes "Handle", but it only provides a brief example in the Rust language, without mentioning what "Handle" value is actually are (e.g. replesentation in .wat file). |
Why are the function types in the wasi API documentation different from the ones I actually compiled in wasm?
The fd_write function in the above document takes two parameters, but the following figure actually takes four.
The text was updated successfully, but these errors were encountered: