Test case:
https://github.com/kripken/emscripten/pull/6419#issuecomment-379610702
--
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
asm.js starting up faster than wasm does sound like a bug, yeah. Is this a
chrome-specific bug? We should file it with a testcase, if possible. (AFAIK
on chrome asm.js should use the wasm pipeline now under the hood, so wasm
being slower is especially weird and indicates a problem.)
On Sat, Apr
I'm using chrome, and I just tested the asm.js build, which, to my
surprise, actually starts up faster than the wasm build ... How can that
be? I mean, maybe I misunderstood something about what wasm is supposed to
deliver, but wasn't faster compile time one of the touted benefits?
On
What browser do you use? For me Chrome is dramatically slow while
compiling wasm, asm.js is faster at least 3 times.
2018-04-08 1:19 GMT+07:00 Goran Milovanovic :
> After all the files are downloaded, it takes ~5 seconds for my program to
> actually start. Since my cpu