From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: Zack Weinberg <zackw@panix.com>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH] Remove support for PowerPC e500 / SPE ISA extension.
Date: Tue, 21 May 2019 15:51:19 -0300 [thread overview]
Message-ID: <915b14c5-515a-b999-4058-7beea1b5cfe9@linaro.org> (raw)
In-Reply-To: <CAKCAbMi9YXWgVXcydkGOd4b08G6wV2iru2PUy8-HosiXHHih4A@mail.gmail.com>
On 21/05/2019 15:22, Zack Weinberg wrote:
> On Thu, May 16, 2019 at 3:22 PM Zack Weinberg <zackw@panix.com> wrote:
>> On Thu, May 16, 2019 at 2:51 PM, Adhemerval Zanella
>> <adhemerval.zanella@linaro.org> wrote:
>> On 16/05/2019 14:54, Zack Weinberg wrote:
>>>> GCC 9 dropped support for the e500 variation of PowerPC, so I suggest
>>>> we should follow suit.
>>>
>>> I was about to send a similar patch. I will do a sanity check on
>>> powerpc-linux-gnu to see if this causes any regressions. It looks ok
>>> imho and I think it align with GCC move regarding the ABI.
>>
>> Thanks for the review. I will wait to hear the results of your sanity
>> check before pushing.
>
> Did you get around to doing this sanity check?
I saw no regressions on powerpc64le-linux-gnu, powerpc64-linux-gnu,
powerpc-linux-gnu, and powerpc-linux-gnu-power4. However, like you
I hit the same issue with powerpc-linux-gnu-soft configuration build
with hard float (link failures). I did not dig into yet.
next prev parent reply other threads:[~2019-05-21 18:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-16 17:54 [PATCH] Remove support for PowerPC e500 / SPE ISA extension Zack Weinberg
2019-05-16 18:51 ` Adhemerval Zanella
2019-05-16 19:22 ` Zack Weinberg
2019-05-21 18:22 ` Zack Weinberg
2019-05-21 18:51 ` Adhemerval Zanella [this message]
2019-05-16 19:59 ` Segher Boessenkool
2019-05-16 20:24 ` Joseph Myers
2019-05-16 21:12 ` Segher Boessenkool
2019-05-16 23:57 ` Zack Weinberg
2019-05-17 0:54 ` Segher Boessenkool
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=915b14c5-515a-b999-4058-7beea1b5cfe9@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.org \
--cc=zackw@panix.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).