This is the mail archive of the
mailing list for the GCC project.
Re: When to emit C++ debug info?
- From: Geoff Keating <geoffk at desire dot geoffk dot org>
- To: sabre at nondot dot org
- Cc: drow at mvista dot com, snyder at fnal dot gov, gcc at gcc dot gnu dot org
- Date: Sat, 3 Jan 2004 17:36:23 -0800
- Subject: Re: When to emit C++ debug info?
- References: <Pine.LNX.firstname.lastname@example.org>
> X-Original-To: email@example.com
> Date: Sat, 3 Jan 2004 19:05:42 -0600 (CST)
> From: Chris Lattner <firstname.lastname@example.org>
> Geoff Keating writes:
> > I think we'll want to be able to do it these ways:
> > - One way where the minimal debugging information is emitted so that
> > when put together, the whole program has complete debugging
> > information; and
> > - Another way where complete information is emitted for a single file.
> > I'm not sure why you'd want something between these two extremes.
> Why not always do #2, and have the linker eliminate the duplicate
Because it makes .o files large, and that makes the linker slow
because it has to process the huge collection of .o files.
- Geoffrey Keating <email@example.com>