Conversation
achille-roussel
approved these changes
May 11, 2023
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.
Following up from #20, this PR adds basic WasmEdge v1 support. We can reliably detect whether the WASM module was compiled with the V1 or V2 API, and setup the necessary host module. The user shouldn't have to do anything, since
--sockets autois the default.V1 is mostly the same; there are a few minor differences. I've left a few stubs/TODOs for later.
I'm now able to run the examples from https://github.com/second-state/wasm-learning and https://github.com/second-state/wasmedge_wasi_socket, and the WasmEdge Python version from https://github.com/vmware-labs/webassembly-language-runtimes/releases: