Why don't you change the source to split up that single large switch statement across multiple functions? The Chrome profiler should then tell you if that was effective, no? You could also try Alon's outlining feature and see if that does the trick without touching the source. I think this was introduced to split large functions into smaller ones in order to make it easier (and faster) for JITs to optimize the code.
Am Samstag, 21. Dezember 2013 20:11:10 UTC+10 schrieb [email protected]: > > So the SID-chip/C64 emulation part of my music player runs very slow - > about 10x native. Checking in the Chrome profiler I see that the main > function has an exclamation mark with: > Not Optimized: SwitchStatement: Too many clauses > > The 6510 emulation core is one big switch statement, so this is true. I > realize this is a JIT problem but I wonder if you can get the emscripten > compiler to help in this situation? > > Otherwise maybe I can try breaking it up manually, but would that help? > > -- Sasq > -- 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/groups/opt_out.
