This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Code Bloat g++
- To: "Martin v. Loewis" <martin at loewis dot home dot cs dot tu-berlin dot de>
- Subject: Re: Code Bloat g++
- From: Branko Čibej <branko dot cibej at hermes dot si>
- Date: Thu, 17 Feb 2000 22:13:24 +0100
- CC: jbuck at possibly dot synopsys dot com, pfeifer at dbai dot tuwien dot ac dot at, NEELAKANTH dot NADGIR at sun dot com, gcc at gcc dot gnu dot org
- Organization: HERMES SoftLab
- References: <200002171554.HAA24367@possibly.synopsys.com> <200002171939.UAA01047@loewis.home.cs.tu-berlin.de>
"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