From: Mark Mitchell <mark@codesourcery.com>
To: gcc-announce@gcc.gnu.org, gcc@gcc.gnu.org
Subject: Target Deprecation
Date: Tue, 11 Mar 2003 19:29:00 -0000 [thread overview]
Message-ID: <1047410075.3197.71.camel@doubledemon.codesourcery.com> (raw)
In the GCC 3.4 release (still some time in the future), the GCC
developers intend to remove a number of obsolete target systems.
Removing these old systems allows the development team to focus its
limited resources to support those systems that are used by more people.
Below, please find the complete list, in the form of GNU target
triplets.
If you feel strongly that support for one of these targets should not be
removed, please contact me by email ASAP. (I will maintain the list.)
Traditionally, GCC has been more receptive to requests that a particular
target not be removed if a volunteer is available to maintain that
target, so if you're interested in volunteering you should state that
explicitly. Also, "there are 1000 of us using this machine heavily all
day long and we were planning to upgrade to GCC 3.4" is probably more
likely to sway the development team than "I think there is still one of
those in my closet." :-)
arc-*-*
i960-*-*
m88k-*-*
romp-*-*
alpha*-*-interix*
alpha*-*-linux*libc1*
alpha*-*-linux*ecoff*
arm*-*-aout*
arm*-*-conix*
arm*-*-oabi
strongarm-*-coff*
hppa1.0-*-osf*
hppa1.0-*-bsd*
hppa1.[01]-*-hpux[789]*
hppa*-*-hiux*
hppa*-*-lites*
hppa*-*-mpeix*
i?86-ncr-*
i?86-sequent-*
i?86-moss-*
i?86-*-netware
i?86-*-freebsd2*
i?86-*-netbsd*aout*
i?86-*-linux*aout*
i?86-*-moss*
i?86-*-sysv3*
i?86-*-interix # not interix3
i?86-*-win32
m68000-hp-bsd*
m68000-hp-hpux*
m68000-sun-sunos*
m68000-att-sysv*
m68k-atari-sysv*
m68k-motorola-sysv*
m68k-ncr-sysv*
m68k-plexus-sysv*
m68k-tti-*
m68k-crds-unos*
m68k-cbm-sysv*
m68k-ccur-rtu*
m68k-hp-bsd*
m68k-hp-hpux*
m68k-sun-mach*
m68k-sun-sunos*
m68k-*-linux*aout*
m68k-*-linux*libc1
m68k-*-psos*
mips*-*-ecoff*
mips-sni-sysv4
mips64orion-*-rtems*
powerpc*-*-sysv* # generic only; consider -elf instead
powerpc*-*-linux*libc1
rs6000-ibm-aix[123]*
rs6000-bull-bosx
rs6000-*-mach*
sparc-*-aout*
sparc-*-netbsd*aout*
sparc-*-bsd*
sparc-*-chorusos*
sparc-*-linux*aout*
sparc-*-linux*libc1*
sparc-*-lynxos*
sparc-hal-solaris2*
sparc-*-sunos[34]*
sparclet-*-aout*
sparclite-*-coff*
sparclite-*-aout*
sparc86x-*-aout*
v850-*-rtems*
vax-*-bsd*
vax-*-sysv*
vax-*-netbsd*aout*
vax-*-vms*
--
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com
reply other threads:[~2003-03-11 19:29 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=1047410075.3197.71.camel@doubledemon.codesourcery.com \
--to=mark@codesourcery.com \
--cc=gcc-announce@gcc.gnu.org \
--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).