http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43601
--- Comment #25 from Dave Korn <davek at gcc dot gnu.org> 2010-09-24 05:00:16 UTC --- I'm going to be working on a patch in this area in the next few weeks (I want to make the dllexport/dllimport attributes work on C++ namespaces), and I can probably do something about this issue while I'm in there anyway. Before I put a bunch of time into that, however, I'd like to see actual diagnosis of what's in the different .o files so that I know that I won't be wasting my time, e.g. what if the extra emitted functions is actually only contributing 10% of this growth in file sizes and the other 90% comes from debug info or EH tables? If something like that did turn out to be the case, then the effort would be wasted as the new option wouldn't actually solve your link-time problems anyway. So I would like to see some proper detailed analysis on object files establishing exactly what constitutes all this bloat and where it comes from before I commit to what might be the wrong path of action. [ Vadim, it's no use sending me off-list mail if your domain doesn't accept replies from gmail.com! Email addresses @gcc.gnu.org are just redirectors to maintainers' primary accounts. ] -- Configure bugmail: http://gcc.gnu.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
