I observed that slow startup of webassembly on Mac chrome canary is due to large amount of time taken in up front compilation. As compared to Windows chrome, the compile time is very high on Mac chrome for small wasm module. Not sure if it is due to hardware or software limitations of Mac. Or a bug in chrome. Is there any js flag in d8 or chrome using which I can find the granular compilation time for each Wasm function in a module? The issue does not happen on Firefox maybe because of indexeddb caching
-- 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.
