From: Stephen & Linda Smith <ischis2@cox.net>
To: Mark Kettenis <mark.kettenis@xs4all.nl>, gdb@sourceware.org
Subject: Re: Likely obsolete pieces of GDB
Date: Sun, 17 Dec 2006 14:26:00 -0000 [thread overview]
Message-ID: <45855465.7090706@cox.net> (raw)
In-Reply-To: <13057.82.92.89.47.1166358029.squirrel@webmail.xs4all.nl>
Mark Kettenis wrote:
>> gnu-v2-abi.c
>> gnu-v2-abi.h
>>
>> C++ ABI support for GCC 2.x.
>>
>> I'm not sure about these. The last release of GCC they worked
>> with was 2.95.3. GCC 3.0 was released Jun 18, 2001. Adoption
>> was slow, but I think I can safely say that almost no one uses
>> 2.95.x any more; even Debian stopped using it three and a half
>> years ago. Should we keep this?
>>
>
> Yes, we should keep this. Several OpenBSD platforms still use GCC 2.95.3.
>
>
The OS that I am working with still uses the 2.95 compiler for the PPC.
Please keep it in.
next prev parent reply other threads:[~2006-12-17 14:26 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-16 20:59 Daniel Jacobowitz
2006-12-16 21:23 ` Christopher Faylor
2007-02-10 21:42 ` Pedro Alves
2007-02-10 23:50 ` Daniel Jacobowitz
2007-02-19 1:25 ` Pedro Alves
2006-12-17 1:24 ` John David Anglin
2006-12-17 11:46 ` Mark Kettenis
2007-01-01 16:34 ` Daniel Jacobowitz
2006-12-18 3:03 ` John David Anglin
2006-12-18 3:43 ` John David Anglin
2006-12-20 16:07 ` John David Anglin
2006-12-20 17:41 ` John David Anglin
2007-01-01 16:33 ` Daniel Jacobowitz
2007-01-01 16:47 ` John David Anglin
2007-01-01 17:10 ` Mark Kettenis
2007-01-01 17:20 ` John David Anglin
2006-12-17 1:36 ` Russell Shaw
2006-12-17 12:20 ` Mark Kettenis
2006-12-17 14:26 ` Stephen & Linda Smith [this message]
2006-12-17 15:37 ` Daniel Jacobowitz
2006-12-20 6:01 ` Joel Brobecker
2006-12-17 13:40 ` Joel Brobecker
2007-01-01 16:46 ` Daniel Jacobowitz
2007-01-01 16:58 ` Mark Kettenis
2007-01-03 23:55 ` Jim Blandy
2007-02-10 20:50 ` Daniel Jacobowitz
2007-02-12 17:35 ` Joel Brobecker
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=45855465.7090706@cox.net \
--to=ischis2@cox.net \
--cc=gdb@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
/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