Hi, from docs: ``` WASM=0 behaves differently in the two backends. In fastcomp we emit asm.js, while in upstream we emit JS (since not all wasm constructs can be expressed in asm.js). Also, the JS support implements the same external WebAssembly.* API, so in particular startup will be async just like wasm by default, and you can control that with WASM_ASYNC_COMPILATION (even though WASM=0). ``` Do you have plan to add support for ASM.JS in non-fastcomp backend? I received feedback that js version of js-dos is much slower then asm.js version of it.
I have 3 version of js-dos now: * asyncify * emterp * nosync So for nosync & emterp version I can compile ASM.JS with fastcomp. Can I also compile asyncify version with fastcomp to asm.js? -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/emscripten-discuss/CAKOm%3DVGGbZvypXnN2HUDSXi%2Bi2j_fhK2SSGuG2xpE1u%2Bud_c8g%40mail.gmail.com.
