From: "Eric Christopher" <echristo@redhat.com>
To: gcc@gcc.gnu.org
Subject: Re: More code removal, mips ecoff support
Date: Fri, 07 Dec 2001 13:43:00 -0000 [thread overview]
Message-ID: <20011207.124717.1789366143.16582@redhat.com> (raw)
In-Reply-To: <15376.46097.482650.386352@bespin.esat.kuleuven.ac.be>
In article <15376.46097.482650.386352@bespin.esat.kuleuven.ac.be>, "Bert
De Knuydt" <Bert.Deknuydt@esat.kuleuven.ac.be> wrote:
> I'd really regret removing ecoff. It would mean the end of Ultrix/MIPS
> support, as far as I understand ...
Is anyone still using it? I mean, bootstrapping up new gcc's every
release? My ultrix box can't even handle a bootstrap.
-eric
--
Fridays are not "pants optional"
next prev parent reply other threads:[~2001-12-07 21:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-07 4:21 Bert De Knuydt
2001-12-07 10:06 ` Joe Buck
2001-12-07 13:01 ` Eric Christopher
2001-12-07 13:43 ` Eric Christopher [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-12-07 3:32 Richard Kenner
2001-12-06 16:11 mike stump
2001-12-07 8:35 ` Michal Moskal
2001-12-07 10:22 ` Daniel Jacobowitz
2001-12-07 18:15 ` Guido Guenther
2001-12-06 15:19 Eric Christopher
2001-12-06 15:59 ` Joseph S. Myers
2001-12-06 17:19 ` DJ Delorie
2001-12-06 19:31 ` Stan Shebs
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=20011207.124717.1789366143.16582@redhat.com \
--to=echristo@redhat.com \
--cc=gcc@gcc.gnu.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).