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: When to emit C++ debug info?

From: Joe Buck <Joe dot Buck at synopsys dot COM>
To: Geoff Keating <geoffk at geoffk dot org>
Cc: Daniel Jacobowitz <drow at mvista dot com>, snyder at fnal dot gov,gcc at gcc dot gnu dot org
Date: Mon, 5 Jan 2004 09:26:58 -0800
Subject: Re: When to emit C++ debug info?
References: <20040103120250.07ec0449.bkoz@nabi.net> <20040103181256.GA25426@nevyn.them.org> <jmoetkwws2.fsf@desire.geoffk.org>

On Sat, Jan 03, 2004 at 01:24:29PM -0800, Geoff Keating wrote:
> 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.

Exactly, and the first option should be the default, since it results
in a faster but fully functional compile-link-debug cycle.

It does not need to be absolutely minimal, of course.

References:
- Re: When to emit C++ debug info?
  - From: B. Kosnik
- Re: When to emit C++ debug info?
  - From: Daniel Jacobowitz
- Re: When to emit C++ debug info?
  - From: Geoff Keating

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