This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Obsoleting unmaintained targets


Dear Jim;
I don't know what this message is all about. I could play the Emperor's new
Clothes with you, but so far as I can tell you are on about accessing
features in some sort of code you mean to change. I am interested in getting
a FORTRAN that runs in Win95. You can probably tell me what wonderful things
your site does as well when there is a download link for that module. I am
not averse to having new knowledge. I had initially to force myself to look
at Linux and have install diskettes but am not brave enough to put it into a
computer as yet. Maybe one day I will have the guts, but what I have is what
I use, not what I meddle with. GNU is compared to Linux, how and in what way
is not certain to me. Why not fill me in on what fabulous wonders are
enabled by the GNU system?
-----Original Message-----
From: Jim Wilson <wilson@specifixinc.com>
To: gcc-announce@gcc.gnu.org <gcc-announce@gcc.gnu.org>
Cc: gcc@gcc.gnu.org <gcc@gcc.gnu.org>
Date: Wednesday, December 03, 2003 10:31 AM
Subject: Obsoleting unmaintained targets


>In the GCC 3.4 release (still some time in the future), the GCC
>developers are obsoleting a number of old unmaintained targets.
>Obsoleting these old systems allows the development team to focus its
>limited resources to support those systems that are used by more people.
>
>These targets can still be configured by using the --enable-obsolete
>option.  If no one steps forward to maintain these targets, they will be
>deleted in a future gcc release.
>
>Below, please find the complete list, in the form of GNU target
>triplets.  This has been extensively revised from the list that was
>originally posted in March.
>
>If you feel strongly that support for one of these targets should not be
>removed, please contact us by email to gcc@gcc.gnu.org.  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." :-)
>
>All targets for these architectures have been obsoleted:
> d30v-*
> dsp16xx-*
> i370-*
> i960-*
>
>Individual targets that have been obsoleted:
> i?86-moss-msdos
> i?86-*-moss*
> i?86-ncr-sysv4*
> i?86-*-netware
> i?86-*-freebsd2*
> i?86-*-freebsd*aout*
> i?86-*-linux*aout*
> i?86-*-linux*libc1*
> # This does not affect Interix3 support which remains.
> i?86-*-interix
> i?86-*-mach*
> i?86-*-udk*
> i?86-*-sysv[123]*
> i386-*-vsta
>
> m68k-hp-hpux*
> m68000-hp-hpux*
> m68k-*-sysv4*
>
> # This is only the a.out netbsd targets, the elf netbsd targets
> # remain.
> m68k*-*-netbsd*
>
> # This is only the default target, which is no longer useful.
> # The *BSD, Ultrix, and Sysv targets remain.
> vax-*-*
>--
>Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com
>


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]