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: Wed, 24 May 2017 15:20:00 -0000 [thread overview]
Message-ID: <a569aa5f-121b-7ea0-401d-79da1f34292b@arm.com> (raw)
In-Reply-To: <CABXYE2XMkTimK2vdZupJ6wOZNkG5m9z=P2aF7fM0jtZFspgz-A@mail.gmail.com>
On 24/05/17 15:18, Jim Wilson wrote:
> On Wed, May 24, 2017 at 6:56 AM, Richard Earnshaw (lists)
> <Richard.Earnshaw@arm.com> wrote:
>> OK. does this need to go in the gcc-8 changes file?
>
> Falkor hasn't shipped yet. I'm dropping features that only existed in
> preproduction NDA hardware, so there isn't anything end user visible,
> and hence I don't think that it needs to be in the release notes.
>
> Jim
>
Fair enough, so what about a minimal back-port to GCC-7 that just
disables the CPU name for aarch32?
R.
next prev parent reply other threads:[~2017-05-24 15:17 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) [this message]
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)
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=a569aa5f-121b-7ea0-401d-79da1f34292b@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).