I used -g on compile, -g4 on link (-g4 during compile would be the same), and I verified I could see the generated source map at the end.
Your app must be hitting something that i can't see on bullet, that is, something must be different in your project. Going from 23 seconds to over 4 minutes means something is going very wrong. Perhaps profiling the stages that take a long time (llvm-link and opt?) could show something, just a guess. - Alon On Tue, Feb 3, 2015 at 5:12 PM, Alecazam <[email protected]> wrote: > Hmm. Did you look at Bullet memory use in Activity Monitor? You might > need a library with more C++11 in it (STL?). It's unclear from the build > suggestions as to whether you put -g4 on both the command and link lines (I > do both). The directions say to use -g on compile, and -g4 on the link. > I don't think I have that specificity in my build scripts, but I wonder if > it could be from setting in on both. I also have -O2 --llvm-opts 2 > --llvm-lto 0 on the compile lines as well. Something is generating a ton > of source to the link phase to accumulate 9GB. opt then sees the results > of that with around 5GB. > > 4m15s link with -g4 set. High memory use reported for llvm-link and opt. > 23s link with -g2 and -g3 set. I don't see the high memory use with > either of these. > > -- > 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.
