cvs.gedasymbols.org/archives/browse.cgi   search  
Mail Archives: djgpp-workers/1998/05/21/09:55:12

Date: Thu, 21 May 1998 16:54:40 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Andris Pavenis <pavenis AT lanet DOT lv>
cc: djgpp-workers AT delorie DOT com
Subject: Re: gcc 2.8.1 outputs are much larger than gcc 2.7.2 ... why ?? (fwd)
In-Reply-To: <B0000030590@stargate.astr.lu.lv>
Message-ID: <Pine.SUN.3.91.980521165059.1049C-100000@is>
MIME-Version: 1.0

On Thu, 21 May 1998, Andris Pavenis wrote:

> Info file about AS tells that unless special command line option is specified
> AS does not include local labels (that begins with 'L') in symbol tables.
> However this behaviour can be overriden by target configuration.
> 
> However it looks that these labels stays in object files for both gcc-2.7.2.1
> and gcc-2.8.1. 

So it seems that the cause is in Binutils, not in GCC.  Robert/Andrew, 
can you advise?  I'm afraid I don't know enough about this to tell.

> Enabling exceptions of course makes object files (for C++) bigger. Without 
> exceptions there were no significant changes in size of object files between
> gcc-2.7.2.1 and 2.8.1.

The message I forwarded claimed that exceptions support adds a lot of 
local labels, and that's why it bloats the binary.

> There is one more problem. I did not suceed to get rid of local labels in
> libstdcxx.a  and  libgpp.a  (I compiled without debugging information).

Let me see if I understand.  Are you saying that you *can* get rid of 
local labels in object files, but not in libstdcxx?  How's that possible?

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019