From: Jeff Law <law@redhat.com>
To: Ulrich Weigand <uweigand@de.ibm.com>, gcc-patches@gcc.gnu.org
Cc: dje.gcc@gmail.com
Subject: Re: [RFA][1/3] Remove Cell Broadband Engine SPU targets
Date: Tue, 03 Sep 2019 14:16:00 -0000 [thread overview]
Message-ID: <1de77c6a-9e03-28cb-66c0-71f257762440@redhat.com> (raw)
In-Reply-To: <20190902201653.10222D802F0@oc3748833570.ibm.com>
On 9/2/19 2:16 PM, Ulrich Weigand wrote:
> Hello,
>
> as announced here: https://gcc.gnu.org/ml/gcc/2019-04/msg00023.html
> we have declared the spu-elf target obsolete in GCC 9 with the goal
> of removing support in GCC 10. Nobody has stepped up to take over
> maintainership of the target.
>
> This patch set therefore removes this target and all references
> to it from the GCC source tree. (libstdc++ and testsuite are
> done as separate patches, this patch handles everything else.)
>
> Tested on s390x-ibm-linux.
>
> OK for mainline?
>
> (Deleted directories omitted from patch.)
>
> Bye,
> Ulrich
>
>
> ChangeLog:
>
> * MAINTAINERS: Remove spu port maintainers.
>
> contrib/ChangeLog:
>
> * compare-all-tests (all_targets): Remove references to spu.
> * config-list.mk (LIST): Likewise.
>
> contrib/header-tools/ChangeLog:
>
> * README: Remove references to spu.
> * reduce-headers: Likewise.
>
> libbacktrace/ChangeLog:
>
> * configure.ac: Remove references to spu.
> * configure: Regenerate.
>
> libcpp/ChangeLog:
>
> * directives.c: Remove references to spu from comments.
> * expr.c: Likewise.
>
> libgcc/ChangeLog:
>
> * config.host: Remove references to spu.
> * config/spu/: Remove directory.
>
> gcc/ChangeLog:
>
> * config.gcc: Obsolete spu target. Remove references to spu.
> * configure.ac: Remove references to spu.
> * configure: Regenerate.
> * config/spu/: Remove directory.
> * common/config/spu/: Remove directory.
>
> * doc/extend.texi: Remove references to spu.
> * doc/invoke.texi: Likewise.
> * doc/md.texi: Likewise.
> * doc/sourcebuild.texi: Likewise.
OK for all 3 patches. Similarly for removing any other remnants you
might find later.
jeff
next prev parent reply other threads:[~2019-09-03 14:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-02 20:17 Ulrich Weigand
2019-09-03 14:16 ` Jeff Law [this message]
2019-10-28 9:38 ` Eric Botcazou
2019-10-08 10:32 ` Thomas Schwinge
2019-10-08 16:29 ` Ulrich Weigand
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=1de77c6a-9e03-28cb-66c0-71f257762440@redhat.com \
--to=law@redhat.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=uweigand@de.ibm.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).