Fwd: [RFC/RFA] Obsolete Cell Broadband Engine SPU targets

[Joel Sherrill]

Hi

We knew this was coming. My recollection is that we have a single BSP this
would impact. But that has already been impacted by SPU being split into a
separate gcc target post GCC 7. And that has not been addressed yet anyway.

What's the plan for SPU?

---------- Forwarded message ---------
From: Ulrich Weigand <uweigand at de.ibm.com>
Date: Tue, Apr 2, 2019 at 4:46 AM
Subject: [RFC/RFA] Obsolete Cell Broadband Engine SPU targets
To: <gcc at gcc.gnu.org>, <gcc-patches at gcc.gnu.org>
Cc: <dje.gcc at gmail.com>, <trevor_smigiel at playstation.sony.com>


Hello,

the spu-elf target in GCC supports generating code for the SPU processors
of the Cell Broadband Engine; it has been part of upstream GCC since 2008.

However, at this point I believe this target is no longer in use:
- There is no supported Cell/B.E. hardware any more.
- There is no supported operating system supporting Cell/B.E. any more.

I've still been running daily regression tests until now, but I'll be
unable to continue to do so much longer since the systems I've been
using for this will go away.

Rather than leave SPU support untested/maintained, I'd therefore
propose to declare all SPU targets obsolete in GCC 9 and remove
the code with GCC 10.

Any objections to this approach?

Bye,
Ulrich


gcc/ChangeLog:

        * config.gcc: Mark spu* targets as deprecated/obsolete.

Index: gcc/config.gcc
===================================================================
--- gcc/config.gcc      (revision 270076)
+++ gcc/config.gcc      (working copy)
@@ -248,6 +248,7 @@ md_file=
 # Obsolete configurations.
 case ${target} in
   *-*-solaris2.10*                     \
+  | spu*-*-*                           \
   | tile*-*-*                          \
  )
     if test "x$enable_obsolete" != xyes; then
-- 
  Dr. Ulrich Weigand
  GNU/Linux compilers and toolchain
  Ulrich.Weigand at de.ibm.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20190402/2992a971/attachment.html>