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

Improve WASM targets #69

Open
titzer opened this issue Jul 13, 2022 · 2 comments
Open

Improve WASM targets #69

titzer opened this issue Jul 13, 2022 · 2 comments

Comments

@titzer
Copy link
Owner

titzer commented Jul 13, 2022

Virgil compiles to WASM and has three different runtime implementations:

(1) rt/wave, the (W)eb(A)ssembly (V)irgil (E)nvironment), a minimal set of imports just to get Virgil running, which was only implemented in Wizard and a bit-rotted version in V8 using the C embedding API.
(2) rt/wasi_snapshot_preview1, an implementation of System against the wasi_snapshot_preview1 API, but it is not complete.
(3) rt/node, an implementation of System against the node.js APIs.

I could use some help with (2), as there are a few things not working. Also, there is no equivalent of chmod, which is a minor thing, but needed to bootstrap the compiler.

Also, I haven't fully tested (3) or made it robust. Could use some help here.

@syrusakbary
Copy link

I could use some help with (2), as there are a few things not working

I didn't have time to look into this yet. But it will be useful to know exactly what is not working. Do you have some insight on this?

@titzer
Copy link
Owner Author

titzer commented Jul 14, 2022

System.fileLoad(), for one, which needs stat to get a file size. Generally the tests in test/wasi/ and test/system were what I was working on before I got sidetracked.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants