Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Per Bothner <per@bothner.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb@sources.redhat.com
Subject: Re: C++ FAIL counts and the effect of demangler fix
Date: Thu, 15 Feb 2001 13:46:00 -0000	[thread overview]
Message-ID: <m2g0hf7gud.fsf@kelso.bothner.com> (raw)
In-Reply-To: <3A8C1E5E.F4A2C5E2@cygnus.com>

Andrew Cagney <ac131313@cygnus.com> writes:

> 	o	I don't want GDB's release schedule in
> 		someway directly tided to GCC's release
> 		schedule.

I think that is unavoidable, given that Gcc 3 has a new and
incompatible C++ ABI.  It is Bad if the current release of Gdb cannot
debug code produced from the current release of Gcc.  Therefore, Gdb
5.1 should be released before or at the same time as Gcc 3.0 is
released, and it needs to have at least tolerable support for the new
C++ ABI.

Otherwise, we may have to live with the situation (and I don't
actually know what the situation is), but make no mistake: This is
a critical issue for many people, Red Hat included.  (OS distributors
may have a hard time switching to Gcc 3.0 if there are critical Gdb
regressions.)
-- 
	--Per Bothner
per@bothner.com   http://www.bothner.com/~per/


  reply	other threads:[~2001-02-15 13:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-14  8:49 Michael Elizabeth Chastain
2001-02-15 10:27 ` Andrew Cagney
2001-02-15 13:46   ` Per Bothner [this message]
2001-02-15 15:06     ` Andrew Cagney
2001-02-15 15:14       ` Per Bothner
2001-02-15 23:35     ` Eli Zaretskii
2001-02-16  0:58       ` Daniel Berlin
2001-02-16  2:32         ` Eli Zaretskii
  -- strict thread matches above, loose matches on Subject: below --
2001-02-14 10:24 Michael Elizabeth Chastain
2001-02-14  8:52 Michael Elizabeth Chastain
2001-02-14 10:06 ` Daniel Berlin
2001-02-14  0:06 Michael Elizabeth Chastain
2001-02-14  7:31 ` Andrew Cagney
2001-02-14  8:28   ` Daniel Berlin

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=m2g0hf7gud.fsf@kelso.bothner.com \
    --to=per@bothner.com \
    --cc=ac131313@cygnus.com \
    --cc=gdb@sources.redhat.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