unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Zack Weinberg <zackw@panix.com>
To: Tulio Magno Quites Machado Filho <tuliom@ascii.art.br>
Cc: GNU C Library <libc-alpha@sourceware.org>,
	Joseph Myers <joseph@codesourcery.com>,
	 Segher Boessenkool <segher@kernel.crashing.org>,
	 Adhemerval Zanella <adhemerval.zanella@linaro.org>
Subject: Re: [PATCH v2] Remove support for PowerPC SPE extension (powerpc*-*-*gnuspe*).
Date: Wed, 22 May 2019 15:10:15 -0400	[thread overview]
Message-ID: <CAKCAbMge7JMyTOKaAMid7Rrv-wwo8Jq9aOTcJztu=caERPW_LQ@mail.gmail.com> (raw)
In-Reply-To: <87ef4qmilv.fsf@linux.ibm.com>

On Wed, May 22, 2019 at 2:47 PM Tulio Magno Quites Machado Filho
<tuliom@ascii.art.br> wrote:
>
> Zack Weinberg <zackw@panix.com> writes:
>
> > GCC 9 dropped support for the SPE extensions to PowerPC, which means
> > powerpc*-*-*gnuspe* configurations are no longer buildable with that
> > compiler.  This ISA extension was peculiar to the “e500” line of
> > embedded PowerPC chips, which, as far as I can tell, are no longer
> > being manufactured, so I think we should follow suit.
> >
> > This patch was developed by grepping for “e500”, “__SPE__”, and
> > “__NO_FPRS__”, and may not eliminate every vestige of SPE support.
> > Most uses of __NO_FPRS__ are left alone, as they are relevant to
> > normal embedded PowerPC with soft-float.
>
> Tested on hard-float variants too and LGTM.
>
> Reviewed-by: Tulio Magno Quites Machado Filho <tuliom@linux.ibm.com>

Pushed, thank you.

zw

      reply	other threads:[~2019-05-22 19:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-22 14:13 [PATCH v2] Remove support for PowerPC SPE extension (powerpc*-*-*gnuspe*) Zack Weinberg
2019-05-22 18:47 ` Tulio Magno Quites Machado Filho
2019-05-22 19:10   ` Zack Weinberg [this message]

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

  List information: https://www.gnu.org/software/libc/involved.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAKCAbMge7JMyTOKaAMid7Rrv-wwo8Jq9aOTcJztu=caERPW_LQ@mail.gmail.com' \
    --to=zackw@panix.com \
    --cc=adhemerval.zanella@linaro.org \
    --cc=joseph@codesourcery.com \
    --cc=libc-alpha@sourceware.org \
    --cc=segher@kernel.crashing.org \
    --cc=tuliom@ascii.art.br \
    /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).