How faster and smaller binaryen can optimize code depends on the type of code, but often it makes a big difference, for example asm2wasm's hello worlds size shrinks to almost half. Speed gains can be similar. (See src/passes in binaryen for details of what optimizations it does.)
Autovectorization is definitely a possibility in the future, certainly worth exploring. Btw, if you try binaryen's optimizer on your compiler's output, I'd be interested to see measurements on how it works. Feedback from different compilers is very helpful. On Thu, Aug 17, 2017 at 6:44 AM, <[email protected]> wrote: > Hi, > > Our compiler directly generates (probably sub-optimal) wasm code. I see > that then binaryen "optimize" in binaryen.js library could possibly be used > to later optimize the code. > > What kind of optimisation and so speed gain can be expect? Will binaryen > possibly to SIMD auto-vectorization optimisations in the future, when SIMD > will be part of wasm spec ? Any other useful optimisation to expect ? > > Thanks. > > -- > 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. > -- 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.
