public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org
Cc: dje.gcc@gmail.com, trevor_smigiel@playstation.sony.com
Subject: [RFC/RFA] Obsolete Cell Broadband Engine SPU targets
Date: Tue, 02 Apr 2019 09:46:00 -0000	[thread overview]
Message-ID: <20190402094614.8550AD802C5@oc3748833570.ibm.com> (raw)

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@de.ibm.com

             reply	other threads:[~2019-04-02  9:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-02  9:46 Ulrich Weigand [this message]
2019-04-02 12:40 ` Richard Biener
2019-04-02 13:14 ` Jeff Law
2019-04-02 14:13 ` Ulrich Weigand
2019-04-02 16:07 ` Andrew Pinski
2019-04-02 16:49 ` Eric Gallager
2019-04-02 17:26   ` Ulrich Weigand
2019-04-02 18:18   ` Jeff Law

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=20190402094614.8550AD802C5@oc3748833570.ibm.com \
    --to=uweigand@de.ibm.com \
    --cc=dje.gcc@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=trevor_smigiel@playstation.sony.com \
    /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).