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 15:14:00 -0000	[thread overview]
Message-ID: <m27l2r7cqs.fsf@kelso.bothner.com> (raw)
In-Reply-To: <3A8C5FCB.9651AA23@cygnus.com>

Andrew Cagney <ac131313@cygnus.com> writes:

> 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.

That seems ok.  I don't think we should hold up 5.1 for "perfect"
3.0 C++ support - in fact it is better, I think, for 5.1 to come
out before Gcc 3.0, as long as it has at least tolerable 3.0 C++
support.

I could list my version of a priority list of C++ features, but
since I'm unlikely to do anything about it, there;s not point.
-- 
	--Per Bothner
per@bothner.com   http://www.bothner.com/~per/


  reply	other threads:[~2001-02-15 15:14 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
2001-02-15 15:14       ` Per Bothner [this message]
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=m27l2r7cqs.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