Code Bloat g++

Branko Branko
Thu Feb 17 13:15:00 GMT 2000


"Martin v. Loewis" wrote:

> > > > Anyway, as Alexandre points out: this is debugging information, so
> > > > what is the problem?
> >
> > Argh!  I am astounded at how many C++ compiler developers make such comments.
> > I am familiar with a commercial project that is at a crisis point because
> > of the massive, massive size of debug information generated by a
> > well-known proprietary C++ compiler (literally gigabytes of debug
> > information for a single medium-to-large application, more than triple the
> > size of the previous release).  Please let's not make g++ suck just as
> > badly.
>
> That assumes that large debug information is redundant to a ridiculous
> degree. I don't know whether this is the case, but until I'm proven
> wrong, I'd always assume that every single bit in the debug
> information serves a purpose.

Perhaps they should disable that well-known compiler's ;-) "debug info for
edit-and-continue" option? I've seen object size come down by a factor of 5--10 ...



--
Branko Čibej                 <branko.cibej@hermes.si>
HERMES SoftLab, Litijska 51, 1000 Ljubljana, Slovenia
voice: (+386 61) 186 53 49   fax: (+386 61) 186 52 70




More information about the Gcc mailing list