Sam Clegg

Looks like we have 8 to 1 for adding this to memory64 proposal. @conrad-watt do you think we need to take this back to the CG or can we simply...

The poll on today's CG meeting was positive (all votes we in favor or neutral) so it looks like we will be going ahead with this.

> * Extend JS-API get/set methods to take i64 values? (might be superseded by an implementation limit) This issue likely requires come consideration. In JavaScript i64 pointers tend to be...

> What is currently done for 64 bit memories in the JS API? I vaguely remember we previously discussed a `2^53` JS implementation limit on memory size, to ensure that...

Closing this issue for now. Implementation will be tracked in #51.

Looks like something went wrong with your building system. `target/test.wasm` is an x86_64 executable, and presumably it is supposed to be a wasm file?

If eliminating the JavaScript glue code that you currently need to write to web APIs is you goal then most of the interesting work in that area is currently happening...

[benchmarks.txt](https://github.com/WebAssembly/memory64/files/9892393/benchmarks.txt)

I think the size regressions are because I was measuring both JS and wasm sizes. I will re-measure with just wasm sizes.

There are several reasons such a difference between the two compiler binaries might exist. Firstly, the emscripten binaries are build against LLVM tip-of-tree so they are built from very different...