From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Segher Boessenkool <segher@kernel.crashing.org>,
gcc@gcc.gnu.org,
"debian-powerpc@lists.debian.org"
<debian-powerpc@lists.debian.org>
Subject: Re: Deprecation of powerpc*-*-*spe*
Date: Wed, 18 Apr 2018 22:42:00 -0000 [thread overview]
Message-ID: <487d60b3-ce50-b799-ad0c-55ab5808f091@physik.fu-berlin.de> (raw)
Hi Jakub!
> As has been discussed in the
> https://gcc.gnu.org/ml/gcc/2017-02/msg00041.html
> https://gcc.gnu.org/ml/gcc-patches/2017-05/msg01227.html
> https://gcc.gnu.org/ml/gcc-patches/2018-04/msg00810.html
> threads and in
> https://gcc.gnu.org/PR81084
> 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:
> https://buildd.debian.org/status/fetch.php?pkg=gcc-8&arch=powerpcspe&ver=8-20180402-1&stamp=1522856967&raw=0
Is there anything in the powerpcspe port that is currently making life for
the users or developers of other code harder?
Thanks,
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
next reply other threads:[~2018-04-18 14:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-18 22:42 John Paul Adrian Glaubitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-04-18 10:24 Jakub Jelinek
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=487d60b3-ce50-b799-ad0c-55ab5808f091@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=debian-powerpc@lists.debian.org \
--cc=gcc@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=segher@kernel.crashing.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).