This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Huge Increase in Unstripped Executable Size G++ 2.95 to 3.2
- From: Daniel Jacobowitz <drow at mvista dot com>
- To: Andi Kleen <ak at suse dot de>
- Cc: Andreas Schwab <schwab at suse dot de>, Jim Wilson <wilson at tuliptree dot org>,gcc at gcc dot gnu dot org, nabeel at netzero dot com
- Date: Fri, 28 Feb 2003 10:29:13 -0500
- Subject: Re: Huge Increase in Unstripped Executable Size G++ 2.95 to 3.2
- References: <20030227.154544.18888.253032@webmail06.lax.untd.com.suse.lists.egcs> <3E5ED96F.9090902@tuliptree.org.suse.lists.egcs> <p73ptpc7rjt.fsf@amdsimf.suse.de> <jeisv4y3hy.fsf@sykes.suse.de> <20030228130640.GA16376@wotan.suse.de>
On Fri, Feb 28, 2003 at 02:06:40PM +0100, Andi Kleen wrote:
> On Fri, Feb 28, 2003 at 01:49:13PM +0100, Andreas Schwab wrote:
> > Andi Kleen <ak at suse dot de> writes:
> >
> > |> Jim Wilson <wilson at tuliptree dot org> writes:
> > |>
> > |> > while DWARF2 debug info is designed
> > |> > to be more compact than stabs,
> > |>
> > |> That's a joke isn't it?
> >
> > You didn't read the whole message, did you?
>
> I think I did. But I believe it is incorrect: the reason
> is that just the object files are much bigger too than with
> stabs, and these cannot be explained by "duplicated includes"
For one thing, if you're saying "should be handled by the preprocessor"
then you don't understand what Jim means by duplicated includes. He's
talking about multiple object files which include the same header; it's
a _linker_ optimization.
There are a number of other ways in which GCC's DWARF-2 output is
crappy, sizewise. Before anyone leaps on me, most of them are because
GDB's DWARF-2 reader is crappy, featurewise. That's being worked on.
Beaten on might be a better term.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer