public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mark Mitchell <mark@codesourcery.com>
To: gcc@gcc.gnu.org
Subject: Target deprecation list
Date: Tue, 15 Apr 2003 10:24:00 -0000	[thread overview]
Message-ID: <200304150722.h3F7MvMX015260@doubledemon.codesourcery.com> (raw)


A month ago, I posted a list of targets proposed for deprecation:

  http://gcc.gnu.org/ml/gcc-announce/2003/msg00001.html

I've received some replies from people who wanted to keep some of the
targets on that list.  I asked the folks that replied whether they
were using recent versions of GCC on their target; if they weren't, I
asked if they planned to do so.  (Some people just want to keep using
GCC 2.7.3, and they somehow thought we were going to take it away from
them.)

Here are the ones we should keep, based on those discussions:

  arc-*-*

  hppa*-*-mpeix*

  i?86-ncr-*
  i?86-sequent-*
  i?86-moss-*
  i?86-*-freebsd2*
  i?86-*-netbsd*aout*
  i?86-*-linux*aout*
  i?86-*-moss*
  i?86-*-sysv3*
  i?86-*-interix # not interix3

  i960-*-*

  m68000-hp-hpux*
  m68k-hp-hpux*

  sparclite-*-coff*

  vax-*-bsd*        
  vax-*-netbsd*aout*
  vax-*-vms*
  vax-*-sysv*

That means we can go ahead and lose both the m88k and ROMP targets
completely, even on the 3.3 branch, if someone is motivated to make
the changes.

The other targets that were on the original list, but not on this
list, can go on the mainline -- but *not* on the 3.3 branch.

Patches that do nothing but remove obsoleted targets are pre-approved,
starting in 48 hours so that in case other maintainers and/or the SC
can remove my pre-approval, if they feel it's inappropriate.

--
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com


             reply	other threads:[~2003-04-15  7:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-15 10:24 Mark Mitchell [this message]
2003-04-15 16:38 ` Michael S. Zick
2003-04-15 21:00 ` Richard Henderson
2003-04-15 21:20   ` Mark Mitchell
2003-04-15 21:47     ` Eric Christopher
2003-04-15 21:43 ` Jeff Epler
2003-04-18  0:14   ` Mark Mitchell
2003-04-18  5:02     ` Jeff Epler
2003-04-18  7:43       ` Mark Mitchell
2003-04-17  8:16 ` Nitin Gupta
2003-04-17 14:01   ` Joel Sherrill
2003-04-23 11:55 Nitin Gupta
2003-04-23 16:09 ` Zack Weinberg

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=200304150722.h3F7MvMX015260@doubledemon.codesourcery.com \
    --to=mark@codesourcery.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).