> It is true that dwarf debugging information is much bigger in size. Thanks for confirming. I had read elsewhere that stabs is more inefficient but clearly that is incorrect.
> But in general you have here different possiblities to solve this. > First of course by the debugging-level switch -g<n>. Yes, this is helpful. The gap between -g1 and -g2 is pretty wide (70MB versus 190MB). Unfortunately -g1 is of pretty limited usefulness, but it may be sufficient for some. > Additionally you > can use object-copy tool to split debugging information into an > separate file. Thanks but it unfortunately won't improve link times, which is where it is hurting most. I've made some improvements to link times by reducing template usage and pushing non-inlined methods out of headers, but the debug EXE size is still pretty huge. > The gstabs information isn't possible for x64, so I would recomment > that you stick to the dwarf-2 information. In 4.4.x and 4.5.x series > there are some tweak about debugging information and inlined code. To > avoid this don't use debugging information (or strip them out into > separate debugging file) for optimization levels >= 1. Good to know, thanks! Aaron ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
