> > Crash is fixed now during build(latest code of inline-small). The > generated wasm using newtool(and this new binaryen) throws an exception 6 > during runtime(and asks to build with -s ASSERTIONS); while the generated > wasm using oldtool(and this new binaryen) seems to be working fine. >
After disabling the unneeded construct (identified in bug1 - which was adding static constructors which we never need - which should be compiled out as dead code ideally) and using llvm-lto, the binary generated (both asm and wasm) from new tool are comparable size (2% larger) with old tool. With this new binaryen,our codebase is able to loose additional 1 or 2% in size; but it throws runtime exception. Without llvm-lto, this new binaryen helps in size but it only brings us midway (that is, it is not self sufficient in size reduction) Just to confirm, does just replacing the contents of binaryen folder (before linking bc files) suffice(bin, /scripts/ and src/js) for testing ? Or is there some cache that we need to flush ? I created binaryen_old and binaryen_new folder and kept switching between them by renaming one of them to binaryen before linking bcs. -- 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.
