From: "Richard Earnshaw (lists)" <Richard.Earnshaw@arm.com>
To: Jim Wilson <jim.wilson@linaro.org>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH, ARM/AArch64] drop aarch32 support for falkor/qdf24xx
Date: Sat, 10 Jun 2017 09:44:00 -0000 [thread overview]
Message-ID: <26836903-3626-75be-a376-d5decca60f8e@arm.com> (raw)
In-Reply-To: <CABXYE2WrqwzT4=J+BjAvbAGZwzKG83KMZ96uU1ycq6Lx6uFfHQ@mail.gmail.com>
On 09/06/17 21:03, Jim Wilson wrote:
> On Thu, May 25, 2017 at 2:25 AM, Richard Earnshaw (lists)
> <Richard.Earnshaw@arm.com> wrote:
>> Having pondered this over night, I think the lowest risk thing to do,
>> provided it applies cleanly to the gcc-7 branch, is just commit the
>> entire patch on the branch and be done with it. The risk from removing
>> this code is pretty minimal and removing it all is the best way of
>> avoiding things like unexpected compiler warnings breaking the build.
>> If it doesn't apply cleanly, then just drop the documentation.
>
> The patch backports cleanly. I've tested the patch on the
> gcc-7-branch, with both armv8 and aarch64 bootstraps and make checks,
> with no regressions. Ok to check in?
>
> Jim
>
OK.
R.
next prev parent reply other threads:[~2017-06-10 9:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-12 3:52 Jim Wilson
2017-05-24 14:12 ` Richard Earnshaw (lists)
2017-05-24 14:20 ` Jim Wilson
2017-05-24 15:20 ` Richard Earnshaw (lists)
2017-05-24 16:05 ` Jim Wilson
2017-05-24 16:30 ` Richard Earnshaw (lists)
2017-05-25 9:29 ` Richard Earnshaw (lists)
2017-06-09 20:03 ` Jim Wilson
2017-06-10 9:44 ` Richard Earnshaw (lists) [this message]
2017-06-12 10:40 ` James Greenhalgh
2017-06-23 21:46 ` Jim Wilson
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=26836903-3626-75be-a376-d5decca60f8e@arm.com \
--to=richard.earnshaw@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jim.wilson@linaro.org \
/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).