Hi, On Tue, 22 Nov 2011, Gary Funck wrote:
> Thanks for the tip. Typically, we don't build with > --enable-checking=all, however ... > > We build with --enable-checking=all when we're testing major changes, > moving GUPC to a new target architecture, etc. > > In the past, it may have been slower, and certainly the final compiler > is slower (probably 3x-5x on average), but the extra checking did help > catch some bugs. Makes sense. What I do for this is to build (--disable-bootstrap) a checking=all compiler and just run the testsuite (or other tests). > FYI, on the *very* long running compilations that I checked, the cc1plus > compiler appeared to be stuck in the garbage collector. > > #1 0x00000000009e838e in gt_ggc_mx_lang_tree_node (x_p=0x7fff268282d0) > at ./gt-cp-tree.h:154 Yeah, =all includes GC checking, which includes always running the garbage collector even when not enough allocation activity was done. It might very well be that the cc1plus frontend leaves more reachable memory live than cc1, making the repeated collection attempts hurt much more than with C only. That's possibly something to investigate. Ciao, Michael.
