From: Eli Zaretskii <eliz@delorie.com>
To: per@bothner.com
Cc: ac131313@cygnus.com, gdb@sources.redhat.com
Subject: Re: C++ FAIL counts and the effect of demangler fix
Date: Thu, 15 Feb 2001 23:35:00 -0000 [thread overview]
Message-ID: <200102160735.CAA01234@indy.delorie.com> (raw)
In-Reply-To: <m2g0hf7gud.fsf@kelso.bothner.com>
> From: Per Bothner <per@bothner.com>
> Date: 15 Feb 2001 13:54:02 -0800
>
> 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.)
If there are important reasons why the next release of GDB should
support the new C++ ABI, then perhaps the GCC team should help Daniel
and others work on the GDB side of this support. Or maybe you should
consider delaying the release of GCC 3.0 in the same manner as you are
suggesting that GDB will delay its release.
This is not an issue with GDB alone. The change of the ABI was in
GCC, so I think the GCC team should share the responsibility for
making GDB support it.
next prev parent reply other threads:[~2001-02-15 23:35 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
2001-02-15 23:35 ` Eli Zaretskii [this message]
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=200102160735.CAA01234@indy.delorie.com \
--to=eliz@delorie.com \
--cc=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