Date: Mon, 21 Oct 1996 18:02:39 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: "Troy D. Van Horn" <trvanhor AT UCollege DOT edu>
Cc: trvanhor AT SNOOPY DOT UCollege DOT edu, djgpp AT delorie DOT com
Subject: Re: V2.01 AS.EXE (2.7) puts local labels in obj. file
In-Reply-To: <9610211525.AA02893@is.elta.co.il>
Message-Id: <Pine.SUN.3.91.961021175938.2800E-100000@is>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On Mon, 21 Oct 1996, Troy D. Van Horn wrote:

> > Do these symbols remain in the stripped executable?  If they don't, maybe 
> > this was just meant to assist in debugging?
> 
> No, they don't, so it's not a real problem, but it probably makes library files
> larger than they need to be, (Hey, I'm an efficiency nut)

If the binary doesn't have this bloat, then where's the efficiency aspect 
here?

> and I don't see how
> they can help in debugging unless one was debugging a hand written assembly
> source.

How else would you look for buggy code produced by the compiler?  And how
in the world can Gas know whether a file it gets as input is a
hand-written assembly source or was produced by cc1/cc1plus from a C/C++
source?