public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Stan Shebs <shebs@apple.com>
To: Richard Henderson <rth@cygnus.com>
Cc: Joe Buck <jbuck@racerx.synopsys.com>,
	Mark Mitchell <mark@codesourcery.com>,
	gcc@gcc.gnu.org
Subject: Re: m68k MacOS target support?
Date: Tue, 12 Sep 2000 19:12:00 -0000	[thread overview]
Message-ID: <39BEE28E.114C1E68@apple.com> (raw)
In-Reply-To: <20000912175540.B8196@cygnus.com>

Richard Henderson wrote:
> 
> On Tue, Sep 12, 2000 at 01:59:02PM -0700, Stan Shebs wrote:
> > So I discussed this with RMS and came up with a obsoletion scheme, where
> > old code is prominently marked as obsolete (by commenting out every
> > line), announced as such in a release, and if nobody has come forward
> > to revive it by the time of the next release, it gets completely removed.
> 
> Personally, I think we ought to immediately nuke all the ports that
> were never updated from gcc 1.x, and that have been commented out in
> the configure file since gcc 2.0.
> 
> Namely: fx80, ns32k-ns-genix, pyramid, tahoe, gmicro.

Of these, I only researched the Pyramid thoroughly enough to determine
that the platform was really and truly dead.  I've been somewhat
conservative, because sometimes we actually hear from someone actively
using a supposedly-vanished type of system.

> There are plenty of others that are also obsolete, but those named
> have had many multiples of years completely and obviously not compiled.

Yeah, they're pretty much just taking up disk space then.

Stan

  reply	other threads:[~2000-09-12 19:12 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-09 12:33 Michael Sokolov
2000-09-11 20:47 ` Stan Shebs
2000-09-11 20:56   ` Michael Meissner
2000-09-11 21:33     ` Mark Mitchell
2000-09-12  0:02       ` lars brinkhoff
2000-09-12  0:15         ` Mark Mitchell
2000-09-12  3:26           ` lars brinkhoff
2000-09-12  7:23             ` Mark Mitchell
2000-09-12 11:16           ` Joe Buck
2000-09-12 11:22             ` Bernd Schmidt
2000-09-12 20:11               ` Mark Mitchell
2000-09-12 13:59             ` Stan Shebs
2000-09-12 17:55               ` Richard Henderson
2000-09-12 19:12                 ` Stan Shebs [this message]
2000-09-12 22:44                 ` "Dead" Ports (was: m68k MacOS target support?) Gerald Pfeifer
2000-09-13  9:26                   ` Jeffrey A Law
2000-09-13  9:33                     ` Bernd Schmidt
2000-09-13 11:40                       ` Stan Shebs
2000-09-13  9:57                     ` Bruce Korb
2000-09-13  3:17                 ` m68k MacOS target support? Joseph S. Myers
2000-09-12 11:48           ` Toon Moene
2000-09-12  7:32         ` Jeffrey A Law
2000-09-12 11:11         ` PDP10 support (was Re: m68k MacOS target support?) Joe Buck
2000-09-13 14:51           ` PDP10 support Gerald Pfeifer
2000-09-14  0:15             ` lars brinkhoff
2000-09-14  7:47               ` Nick Ing-Simmons
2000-09-12  0:03       ` m68k MacOS target support? lars brinkhoff
2000-09-12  9:52   ` David Huggins-Daines
2000-09-12  8:11 Richard Kenner
2000-09-12 17:57 Michael Sokolov
2000-09-12 18:12 ` Richard Henderson
2000-09-12 18:19 ` Geoff Keating
2000-09-12 19:05 ` Stan Shebs
2000-09-12 18:08 Michael Sokolov
2000-09-12 18:18 Michael Sokolov
2000-09-12 18:43 Michael Sokolov
2000-09-12 19:44 ` Stan Shebs
2000-09-13  8:40 ` Joe Buck
2000-09-13  8:49 Michael Sokolov

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=39BEE28E.114C1E68@apple.com \
    --to=shebs@apple.com \
    --cc=gcc@gcc.gnu.org \
    --cc=jbuck@racerx.synopsys.com \
    --cc=mark@codesourcery.com \
    --cc=rth@cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).