4 ms·
Actually it was much faster some time ago. At least on Firefox. This emulator is basically a microbenchmark of the switch/case implementation of the browser. Fi
by s-macke 7y ago
Actually it was much faster some time ago. At least on Firefox. This emulator is basically a microbenchmark of the switch/case implementation of the browser. Firefox used a computed goto, which is perfect in this case. Now for some reasons it got slower. I have to take a look at the generated code to be really sure about what is happening here and what to do about it.
- hoistbypetard 7y agoThat is really interesting. I was using it in vivaldi on desktop and chrome on android, fwiw. I have to wonder what wasm might help... maybe the additional overhead on the VT and framebuffer would be so high it'd be a wash.
- s-macke 7y agoWebAssembly does not work on this low level. You cannot choose the switch/case implementation. Also it doesn't support goto. The reason is security and speed. The wasm-binary should be checked in O(n) and not in O(n^2). But I am curious about the future versions of webassembly. There is already a wasm version of the CPU emulation. I will enable it at some point as default. But there is no speedup yet.