Very cool! I have switched the Tiny Emulators page ( https://floooh.github.io/tiny8bit/) to upstream-llvm a couple weeks ago,and it worked out of the box. It's not a very complex code base, but it's not completely trivial either, lots of bit-twiddling on 64-bit integers, quite a few EM_JS calls, closure pass, and lots of Dear ImGui C++ code in the debugging UIs.
I'm happy with the performance now too, it's within 10..20% of a native -O3 build on Chrome, size also looks good (it's a tiny bit smaller than before). For some reason fastcomp didn't like this particular type of code (however, it could also be that this is because the WASM implementation in Chrome has improved, I haven't done side-by-side tests in the same Chrome version yet). Cheers, and keep up the good work :) On Tuesday, 23 July 2019 19:20:25 UTC+2, Alon Zakai wrote: > > Hello everyone, > > After we stabilized the new build machines we've been asking people to > test the new upstream LLVM wasm backend more, > > https://v8.dev/blog/emscripten-llvm-wasm > > The main bugs are being tracked here: > > https://github.com/emscripten-core/emscripten/projects/1 > > The blockers there should be fixed before we switch emsdk's default from > fastcomp to upstream. We've been making good progress, but definitely the > increased testing has found issues we were not aware of earlier, in > emscripten, LLVM, and wasm-ld. > > Please continue to test and file issues, and help with the existing issues > is very welcome! > > - Alon > > -- 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/8a82a237-56b0-4a2b-98c9-396d7196b9e1%40googlegroups.com.
