This is the mail archive of the gcc@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: 3.2 code bloat from debug info

From: Jim Wilson <wilson at specifixinc dot com>
To: Glenn Burkhardt <glenn at aoi-industries dot com>
Cc: gcc at gcc dot gnu dot org
Date: Sat, 29 Nov 2003 14:39:47 -0800
Subject: Re: 3.2 code bloat from debug info
References: <20031129064117.528934B363@berman.michael-chastain.com> <20031129181740.1212A1800B0@aoi-industries.com>

Glenn Burkhardt wrote:

                 2.96            2.98            3.3.2           3.3.2
		dwarf-2          stabs+         dwarf-2          stabs+
dclock.o        121684           131812         252108		278964	
main.o		133392		 143388		263548		294596
moc_dclock.o	158896		 170160		293108		330356

Looking at .o files is misleading. For stabs, we have link time optimizations to eliminate duplicate debug info. We do not yet have this for dwarf2. The result is that after linking the stabs debug info is likely to be significantly smaller than the dwarf2 debug info. -- Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com

Follow-Ups:
- Re: 3.2 code bloat from debug info
  - From: Glenn Burkhardt

References:
- Re: 3.2 code bloat from debug info
  - From: Michael Elizabeth Chastain
- Re: 3.2 code bloat from debug info
  - From: Glenn Burkhardt

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