Sam Clegg

Using node-wasi on the WebAssembly waterfall

3

I've been working on a similar affort to support wasi in JS. Currently we use it to test generated wasm modules on the WebAssembly waterfall: https://github.com/WebAssembly/waterfall/blob/master/src/wasi.js https://wasm-stat.us/console I was previously...

Unable to merge latest spec repo changes

1

When trying to run `update-tests.sh` in https://github.com/WebAssembly/testsuite the memory64 tests could not be updated to do unresolved conflicts merging `spec/master`. ``` >> git reset origin/main --hard HEAD is now at...

wasm2js: Generalize to allow 2-level imports

1

This removes any hard-coded references to `env` (the mangic module name used by llvm and emscripten) and instead imports from whatever module name is used in import declaration.

From the emscripten test suite: ``` $ ./test/runner wasm64.test_eval_ctors_no_main --skip-slow Test suites: ['test_core'] Running test_core: (1 tests) (checking sanity from test runner) shared:INFO: (Emscripten: Running sanity checks) test_eval_ctors_no_main (test_core.wasm64) ......

Implement the standard wasm C++ API in wabt interpreter

3

See https://github.com/WebAssembly/wasm-c-api

Adding some validation of custom sections (e.g. linking section)

3

wabt currently knows how to parse some custom sections, such as the linking section which are outside of the core spec. I'd like to add some amount of validation there...

Emscripten_UpdateWindowFramebuffer fails if pixel data is higher than 2gb in address space

1

Specifically the line `var src = pixels >> 2` needs updating. It should probably be: ``` #if __wasm64__ var src = pixels / 4; #else var src = pixels >>>...

Phase 4 entry requirements have vauge/unclear wording

2

From phase 4 entry requirements: https://github.com/WebAssembly/meetings/blob/main/process/phases.md#4-standardize-the-feature-working-group ``` The formalization and the reference interpreter are usually updated (though these two can be done as part of step 3 at the Working...

This was originally discussed in https://github.com/WebAssembly/JS-BigInt-integration/issues/12. I would like to propose revisiting but since that repo has been archived I'm restarting the conversation here. I've worked on getting memory64 working...