Found the solution: the memory block has to be taken from inside the WebAssembly module...
Le mercredi 13 juillet 2016 16:11:14 UTC+2, [email protected] a écrit : > > Hi, > > I am trying to convert our Faust (faust.grame.fr) to asm.js compilation > chain to WebAssembly. Basically what I am doing is : > > 1) Faust DSP ==> asm.js code using the Faust asm.js backend; > > 2) binaryen tool asm2wasm to convert the asm.js module to a wasm textual > file > > 3) binaryen tool wasm-as to convert the wasm textual file to binary > > 3) load the wasm binary into a html page that we already have to connect > the code to the WebAudio API (so basically wrapping asm.js/WebAssembly > module to create a ScripProcessor node) > . > The bizarre thing is that we get memory access errors when the actual > WebAssembly module is used, so when calling functions from the module. > Actually is is not clear how the following function previously used in > asm.js has to be "adapted" : > > function AsmModule(global, foreign, buffer) {...} > > That is an asm.js module was supposed to be called with a "buffer" > parameter, what has to be done to give the WebAssembly module access to the > ArrayBuffer memory? > > Thanks. > > > -- You received this message because you are subscribed to the Google Groups "emscripten-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
