Yeah, I'm currently not testing with my own compiled Firefox, just the current Nightly, I guess there's a delay when the latest Binaryen changes hit Nightly (or Chrome Canary).
Am Montag, 11. April 2016 20:40:09 UTC+2 schrieb Alon Zakai: > > For firefox, if you use the same build to both create the wasm file and > run it (i.e. the same for spidermonkey shell that binaryen calls to, and > the browser you then run it in), then it should work - if not, that's a > bug. But if it's different builds, then this is expected, the binary format > will be constantly changing until it is stable. > > For chrome, it's a little trickier since the tool to emit wasms is in a > side repo, I'm not sure how to verify that they are in sync. > > For both, there will be "checkpoints" in time where all tools and all > browsers (latest versions of all) should work. The intention is that at > each such point, you'll be able to emit a binary by emcc+binaryen and run > it in browsers, without needing extra tools. Next checkpoint is 0xb, > probably a few weeks away. > > On Sun, Apr 10, 2016 at 4:33 AM, Floh <[email protected] <javascript:>> > wrote: > >> I'm not sure if a .wast file (ASCII) can run directly, I only tried .wams >> (binary), but I think the general workflow still applies. >> >> However I'm currently getting validation errors both in Firefox and >> Chrome with the latest Binaryen and Spidermonkey tools. >> >> For instance in Chrome: >> >> InfiniteSpheres.js:137 Uncaught WasmModule::Instantiate(): Compiling WASM >> function #19:<?> failed:Result = ExprI32ReinterpretF32[0] expected type >> f32, found ExprGetLocal of type f64 @+62 >> >> And in Firefox: >> >> TypeError: wasm validation error at offset 213331: type mismatch: >> expression has type f64 but expected f32 >> >> Cheers, >> -Floh. >> >> Am Samstag, 9. April 2016 09:37:09 UTC+2 schrieb Gareth Morgan: >>> >>> Is this still the best path to follow to run a .WAST file in Chrome >>> Canary? >>> >>> On Friday, March 18, 2016 at 3:25:08 AM UTC-7, Floh wrote: >>>> >>>> For reference: here are the requires steps to compile the Oryol samples >>>> for WebAssembly, please ignore all the 'little hacks' I wrote about in >>>> this >>>> thread :) >>>> >>>> http://floooh.github.io/2016/03/17/oryol-webassembly.html >>>> >>>> Cheers, >>>> -Floh. >>>> >>>> Am Dienstag, 15. März 2016 18:26:37 UTC+1 schrieb Floh: >>>>> >>>>> Hi, >>>>> >>>>> I'm currently playing around with binaryen to compile my demos to >>>>> WebAssembly, but it looks like this can only generate .wast (text) files, >>>>> is this correct? >>>>> >>>>> Is there a already way to create binary .wasm file with the help of >>>>> emscripten? >>>>> >>>>> I would *really* like to test my stuff with the new experimental >>>>> WebAssembly support in Firefox Nightly and Chrome Canary :) >>>>> >>>>> Cheers, >>>>> -Floh. >>>>> >>>> -- >> 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] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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.
