From: Steinar Bang <sb@metis.no>
To: gcc@gcc.gnu.org
Cc: gdb@sources.redhat.com
Subject: Re: Which version of gdb supports gcc 3.0 ABI?
Date: Wed, 21 Mar 2001 15:59:00 -0000 [thread overview]
Message-ID: <whvgpavpg6.fsf@viffer.computas.no> (raw)
In-Reply-To: <200103150907.EAA27838@indy.delorie.com>
>>>>> Eli Zaretskii <eliz@delorie.com>:
> FWIW, I always had the GDB patches I posted as an RFA approved or
> commented on in reasonable time (i.e. about a week).
> In any case, a fork is not something people should consider easily,
> just because someone's patch is not accepted quickly enough.
Maybe so.
But the lack of C++ support for gcc 3.0 is a problem.
And it will become a _huge_ problem when gcc 3.0 is released.
It must be adressed in some way, I think. And a fork sounds like the
best alternative.
In a fork like this, one doesn't have to take into consideration
support for other languages in the common code. Once the fork is
actually working for C++ in gcc 3.0, one can look into what changes
needs to be made in the common part of gdb, and argue for them, and
possibly work towards merging the new C++ support into the mainstream.
A fork doesn't _have_ to end up like GNU Emacs and XEmacs. It could
be like with egcs and gcc (ie. first a fork and then a merge).
next prev parent reply other threads:[~2001-03-21 15:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200103131956.f2DJuCT31263@fillmore.constant.com>
[not found] ` <m2wv9tv0a7.fsf@dynamic-addr-83-177.resnet.rochester.edu>
[not found] ` <20010314132500.D6148@disaster.jaj.com>
2001-03-21 15:59 ` Christopher Faylor
2001-03-21 15:59 ` Daniel Berlin
2001-03-21 15:59 ` Eli Zaretskii
2001-03-21 15:59 ` Steinar Bang [this message]
2001-03-21 15:59 ` Andrew Cagney
2001-03-21 15:59 ` Christopher Faylor
2001-03-21 15:59 ` Eli Zaretskii
2001-03-21 15:59 ` Eli Zaretskii
2001-03-21 15:59 Michael Elizabeth Chastain
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=whvgpavpg6.fsf@viffer.computas.no \
--to=sb@metis.no \
--cc=gcc@gcc.gnu.org \
--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