wasm-e2e icon indicating copy to clipboard operation
wasm-e2e copied to clipboard

Published 20 hours ago • verified publisher icon binji

Examples fail with ReferenceError: _WASMEXP_ is not defined

Open ossy-szeged opened this issue 8 years ago • 6 comments

$ scripts/run.py test/fizzbuzz.c /home/oszi/wasm/wasm-e2e/test/wasm.js:46: ReferenceError: WASMEXP is not defined m = WASMEXP.instantiateModule(readbuffer(arguments[0]), ffi); ^ ReferenceError: WASMEXP is not defined at /home/oszi/wasm/wasm-e2e/test/wasm.js:46:5

ossy-szeged avatar Mar 11 '16 12:03 ossy-szeged

In V8 we've recently renamed the WASMEXP object to simply "Wasm".

titzer avatar Mar 11 '16 12:03 titzer

This is already updated in sexpr-wasm-prototype, so maybe just wasm-e2e needs to be updated.

titzer avatar Mar 11 '16 12:03 titzer

Ah, wasm-e2e uses fixed binaryen and sexpr-wasm-prototype revision with trunk v8. It isn't good at all. I tried to use trunk binaryen and sexpr-wasm-prototype too, but didn't manage to get a working version.

Is it documented anywhere which revisions of these tools are compatible with each other?

ossy-szeged avatar Mar 25 '16 13:03 ossy-szeged

wasm-e2e hasn't really been updated in a while. If you want to test integration between v8, sexpr-wasm, binaryen, emscripten, and LLVM, it might be easier to try the continuous build waterfall script at https://github.com/WebAssembly/waterfall which does something similar.

dschuff avatar Mar 25 '16 16:03 dschuff

Yeah, maybe we should remove this repo? No one is updating it, and it is confusing when people find it and nothing works.

binji avatar Mar 25 '16 16:03 binji

I'm not a fan of deleting things from the Internet. I'd rather have a warning :)

jfbastien avatar Mar 25 '16 16:03 jfbastien