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

Per Bothner wrote:
> 
> 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.

As far as I know, GDB works tolerably well now for 3.0 - it doesn't dump
core for instance :-).  I'm just geting in and being clear to people
that think 3.0 C++ support perfect needs to be perfect for 5.1 :-)

One likely reality is that: GDB 5.1 will come out, GCC 3.0 will come out
and then a GDB 5.2 will appear.

enjoy,
	Andrew


  reply	other threads:[~2001-02-15 15:06 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
2001-02-15 15:06     ` Andrew Cagney [this message]
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=3A8C5FCB.9651AA23@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=gdb@sources.redhat.com \
    --cc=per@bothner.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