Add WASM WASI backend#63
Open
AlecGhost wants to merge 1 commit into
Open
Conversation
Author
|
I can also upload my runtime and wit folder to resources, if requested. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The WASM WASI backend executes WASM directly in a VM, with access to the OS, instead of through Javascript.
The component model is used to compose a runtime with the Javalette program.
Note: I didn't get Docker running for this repo in the first place, so I only tested this locally on my Apple Silicon machine.
Tools required
wasm-toolswacwasmtimeSetup
The tools expect the
runtime.wasmto be a component.The interface descriptions should be located in a folder named
wit(relative to the path provided).The wit file for the Javalette program must be located in the root of the
witdir and must contain a world namedprogram.The wit files for the runtime and its dependencies must be located in
wit/deps/. It is advised to fetch them with the toolwit-depsto get the right files in the right places.