From: Mark Mitchell <mark@codesourcery.com>
To: gcc-announce@gcc.gnu.org
Subject: Removal of support for certain architectures
Date: Thu, 21 Sep 2000 18:20:00 -0000 [thread overview]
Message-ID: <20000920091533A.mitchell@codesourcery.com> (raw)
There are some architectures that GCC supported in the past, but that
it has not supported for many years. The files containing machine
descriptions and related information have remained in the source tree,
which causes confusion since users and maintainers alike are unsure as
to the status of these ports.
Therefore, the Steering Committee has decided to remove these files.
Because the GCC project uses CVS, these files can always be
resurrected, if that proves useful in the future.
The machines in question are:
fx80
ns32k-ns-genix
pyramid
tahoe
gmicro
spur
If you believe that there is a compelling reason why the files to
support these architectures should not be removed -- despite the fact
that they do not actually work with any recent version of GCC and that
the files will remain in CVS for posterity -- please let me know as
soon as possible by sending email to `mark@codesourcery.com'.
Thank you,
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com
reply other threads:[~2000-09-21 18:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20000920091533A.mitchell@codesourcery.com \
--to=mark@codesourcery.com \
--cc=gcc-announce@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).