This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

RE: FW: Huge binaries

From: "Hite, Christopher" <Christopher dot Hite at partner dot commerzbank dot com>
To: "Ian Lance Taylor" <iant at google dot com>
Cc: <gcc-help at gcc dot gnu dot org>
Date: Mon, 21 Feb 2011 17:37:52 +0100
Subject: RE: FW: Huge binaries
References: <A2C39688B74331498D789F553EF7B40D14DD4E@SE003331.ztb.icb.commerzbank.com> <mcr4o7x4avr.fsf@google.com>

> There is certainly more debug info generated by gcc 4.5.2.  Are you
saying that your stripped binary went from 60MB to 1200MB without
counting any debug info?  That seems difficult to understand.  If that
is what happened you're 
> going to need to track down the specific part of your program which
increased that much.  Using nm --size-sort may help.

No the stripped binary is with the old and new compiler is 60MB.  That
seems to be the size of my code.  So it's not an issue code bloat issue.
The binary with debug info goes from 180MB to  1200MB when I upgrade the
compiler.

I can see the .o files having to do with my MPL generated en/decoder are
huge.

Does debug information affect performance in any way?

Chris

Follow-Ups:
- Re: FW: Huge binaries
  - From: Andrew Haley
- Re: FW: Huge binaries
  - From: Ian Lance Taylor

References:
- FW: Huge binaries
  - From: Hite, Christopher
- Re: FW: Huge binaries
  - From: Ian Lance Taylor

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]