- yes autovectorization usually helps a lot with this kind of code, as we can see when we produce C/C++ code from the Faust compiler.
- code size is usually not an issue, but speed is - for speed measurement, should I simply use all Date.getTime kind of API ? Or are they any more sophisticated tools available in the different browsers ? (or Node.js maybe ?) Thanks. Le jeudi 17 août 2017 21:56:59 UTC+2, Alon Zakai a écrit : > > Interesting, I see. Yes, it does sound like autovectorization could be > important for code like that. > > I would measure code size after running binaryen's optimizer (say, > wasm-opt -Oz) on your output. Or are these usually small programs anyhow, > and code size isn't an issue for you? If you have existing benchmarks then > measuring the speed of the optimized binaries is also interesting. > > > On Thu, Aug 17, 2017 at 9:31 AM, <le...@grame.fr <javascript:>> wrote: > >> Our compiler (for the Faust DSP audio language http://faust.grame.fr/ >> <http://faust.grame.fr/modules/faustlive-wasm.html>) generates numerical >> processing code. Precompiled pages containing Faust generated WebAudio >> nodes can be found here: http://faust.grame.fr/modules/, using the RUN >> button to load actual pages with the JS + wasm WebAudio node. >> >> The compiler itself (compiled with Emscripten) is usable here: >> http://faust.grame.fr/modules/faustlive-wasm.html. URL for the DSP on >> the modules page can be used, by just doing a "drag/drop" from the "FAUST" >> button (the actual .dsp file URL) to the drop zone. >> >> What measurements tools do you advice to use? >> >> Thanks. >> >> Le jeudi 17 août 2017 17:14:50 UTC+2, Alon Zakai a écrit : >>> >>> 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, <le...@grame.fr> 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 emscripten-discuss+unsubscr...@googlegroups.com. >>>> 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 emscripten-discuss+unsubscr...@googlegroups.com <javascript:>. >> 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 emscripten-discuss+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
