Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Michael Elizabeth Chastain <mec.gnu@mindspring.com>
Cc: jimb@redhat.com, eliz@gnu.org, ezannoni@redhat.com,
	gdb-patches@sources.redhat.com
Subject: Re: [RFA/dwarf] Eliminate dwarf2_tmp_obstack
Date: Mon, 19 Apr 2004 18:27:00 -0000	[thread overview]
Message-ID: <20040419182705.GA1966@nevyn.them.org> (raw)
In-Reply-To: <20040419182621.6D1704B104@berman.michael-chastain.com>

On Mon, Apr 19, 2004 at 02:26:21PM -0400, Michael Chastain wrote:
> Daniel Jacobowitz writes:
> > That's OK, you're right on all counts anyway.  The bug does not render
> > GCC 2.95 code undebuggable; it just interferes with prologue skipping
> > and setting breakpoints on the first line of functions, in some cases. 
> > Both of which are testsuite is heavily biased towards.
> 
> Ummm, just to be clear, you're not about to make the test results worse
> with gcc 2.95.3, are you?

No.  It was a parenthetical comment.  It has nothing to do with any
submitted patch.

> BTW, gcc 2.95.3 on native i686-pc-linux-gnu does indeed default to
> stabs+, but who knows what the default is on various distros.  And here
> is a quick list of some gcc-2 based distros: freebsd 4, netbsd 1.6,
> openbsd 3.4, debian 3.0, vine 2.6, gnoppix 0.6, lindows 4.5,
> lycoris build3.

I do not know of any Linux distribution which changed the default to
dwarf2.

> My personal estimate/opinion is that gdb HEAD can drop support for gcc 2
> some time around October 2005.

"Making the test results worse" is a far cry from "dropping support".

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2004-04-19 18:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-19 18:25 Michael Elizabeth Chastain
2004-04-19 18:27 ` Daniel Jacobowitz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-04-19 18:33 Michael Elizabeth Chastain
2004-04-19  3:17 Daniel Jacobowitz
2004-04-19  5:55 ` Eli Zaretskii
2004-04-19 12:42   ` Jim Blandy
2004-04-19 13:18     ` Daniel Jacobowitz
2004-04-19 12:42 ` Jim Blandy
2004-04-19 13:21   ` Daniel Jacobowitz
2004-04-19 18:15     ` Jim Blandy
2004-04-19 23:30       ` Daniel Jacobowitz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040419182705.GA1966@nevyn.them.org \
    --to=drow@false.org \
    --cc=eliz@gnu.org \
    --cc=ezannoni@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jimb@redhat.com \
    --cc=mec.gnu@mindspring.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox