This is the mail archive of the
mailing list for the GCC project.
Re: Deprecation of powerpc*-*-*spe*
- From: John Paul Adrian Glaubitz <glaubitz at physik dot fu-berlin dot de>
- To: Jakub Jelinek <jakub at redhat dot com>
- Cc: Segher Boessenkool <segher at kernel dot crashing dot org>, gcc at gcc dot gnu dot org, "debian-powerpc at lists dot debian dot org" <debian-powerpc at lists dot debian dot org>
- Date: Wed, 18 Apr 2018 16:54:38 +0200
- Subject: Re: Deprecation of powerpc*-*-*spe*
As has been discussed in the
threads and in
the powerpc*-*-*spe* support which has been split into a separate backend
hasn't been given enough maintainance and so is deprecated in GCC 8.
I'm surprised that these topics are hardly ever discussed with downstream
projects like Debian. I am maintaining powerpcspe in Debian and the port
is very stable for us.
There are people running the port on embedded PowerPC e500 systems like
A-EON Tabor A1222 or the powerpc-based Turris router so killing off
gcc support would mean that these people can no longer run an updated
version of Debian on their machines.
I also don't know why the port is considered to be broken. I haven't run
the testsuite for binutils or gcc recently, true, but gcc-8 works just
fine on powerpcspe and is actually the only current compiler we have since
the powerpcspe support in LLVM is incomplete.
Here's the build log of gcc-8 (20180402) built natively on PowerPC e500
just two weeks ago:
Is there anything in the powerpcspe port that is currently making life for
the users or developers of other code harder?
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - email@example.com
`. `' Freie Universitaet Berlin - firstname.lastname@example.org
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913