Sean McBride

Not intended to be merged! This branch contains changes to support patches to the WebAssembly spec and toolchain to use 4K pages in place of 64k.

Absolutely broken, and I'm unclear if this is even workable TBH! 😅

Given the shift to WASI and the uvwasi backing, we can potentially remove wasmception from the runtimes in this repo.

Feature: Multi Value

1

This feature enables a WebAssembly function to return a tuple of values. When writing WebAssembly by hand, I've found this to be a helpful way to return an `(i32, i32)`...

As of this comment, `wasmparser` is on `0.83.0`. Given that a release that may contain breaking changes occurs every month, this may be a higher version when you read this....

This is a higher-level post MVP feature that may not make sense for us. The idea of a reference is that a WebAssembly sandbox can be passed an opaque host...

Including for completeness, but this is a very large surface area of instructions and is not expected to be beneficial to our research. Reference: https://github.com/webassembly/simd

This proposal may offer some performance improvements. I think the way we codegen passive data segments as initializer functions should map to the behavior below, but would require deeper study....

- `i32.trunc_sat_f32_s` - `i32.trunc_sat_f32_u` - `i32.trunc_sat_f64_s` - `i32.trunc_sat_f64_u` - `i64.trunc_sat_f32_s` - `i64.trunc_sat_f32_u` - `i64.trunc_sat_f64_s` - `i64.trunc_sat_f64_u` Also need to verify that the alternative conversion instructions trap as expected Reference: https://github.com/WebAssembly/nontrapping-float-to-int-conversions/blob/master/proposals/nontrapping-float-to-int-conversion/Overview.md