Re: Trying to understand invoke_* wrappers

2018-10-10 Thread Heejin Ahn
They are generated for exception handling support. You can pass '-s DISABLE_EXCEPTION_CATCHING=1' to emcc, but I think this is already the default, so I'm not sure why you are getting that. On Wed, Oct 10, 2018 at 11:20 AM stephen.weber via emscripten-discuss <

Trying to understand invoke_* wrappers

2018-10-10 Thread stephen.weber via emscripten-discuss
Hello! I am trying to compile some C code with emscripten to use with a non-browser WASM VM, so I can't use the generate JS shims and have to fill in anything actually needed on my own. The bulk of what I need after an `-O3` is not a big deal (Math.pow and such) but all of the invoke_*

Re: Removal of EMSCRIPTEN_ROOT from config file

2018-10-10 Thread Floh
Does this fix change the behaviour of the the "--em-config" and "--cache" cmdline args of emcc and emar to point to a local emscripten SDK install? For me it's important that I don't have that "one and only" central emscripten SDK, but separate versions per "workspace", and I'm using the

Re: Stability of llvm-lto

2018-10-10 Thread Floh
I'm compiling all my stuff with "--llvm-lto 1" and haven't seen problems so far, so from my point of view it's robust. My code isn't very complex but at least the Oryol samples have a nice assortment of 3rd party libs (e.g. Bullet Physics and several UI frameworks):

Re: Removal of EMSCRIPTEN_ROOT from config file

2018-10-10 Thread Beuc
Hi, I believe we'd need to deal with LLVM_ROOT as well, since the fastcomp version needs to be in sync with emscripten's? - Sylvain On 10/10/2018 02:41, Sam Clegg wrote: > TLDR: There is a field in called EMSCRIPTEN_ROOT in the config file > which in theory can be used by external tools to find