From: Mike Stump <mikestump@comcast.net>
To: Andrew Stubbs <ams@codesourcery.com>
Cc: Mike Stump <mikestump@comcast.net>,
Jiong Wang <jiong.wang@arm.com>,
James Greenhalgh <James.Greenhalgh@arm.com>,
Richard Earnshaw <Richard.Earnshaw@arm.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [arm][patch] fix arm_neon_ok check on !arm_arch7
Date: Fri, 28 Nov 2014 08:42:00 -0000 [thread overview]
Message-ID: <A16F5D6F-B1D1-4EAA-9D2B-5FC65F98EC84@comcast.net> (raw)
In-Reply-To: <54775F37.4080001@codesourcery.com>
On Nov 27, 2014, at 9:28 AM, Andrew Stubbs <ams@codesourcery.com> wrote:
> On 27/11/14 17:05, Mike Stump wrote:
>> Could you include a link or the patch. If the test suite, I'll review it if no one else steps up.
>
> The original patch is here:
>
> https://gcc.gnu.org/ml/gcc-patches/2014-09/msg01119.html
Sorry, arm people will have to approve... Many reasonable choices, yet I bet only one is best.
next prev parent reply other threads:[~2014-11-28 5:11 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-13 21:39 Andrew Stubbs
2014-09-15 9:46 ` Richard Earnshaw
2014-09-15 10:56 ` Andrew Stubbs
2014-09-15 13:30 ` Richard Earnshaw
2014-09-17 11:00 ` Andrew Stubbs
2014-09-23 8:27 ` James Greenhalgh
2014-09-23 15:22 ` Stubbs, Andrew
2014-10-15 16:37 ` Jiong Wang
2014-10-15 16:59 ` Andrew Stubbs
2014-10-16 13:53 ` Jiong Wang
2014-11-07 10:35 ` Andrew Stubbs
2014-11-14 11:17 ` Andrew Stubbs
2014-11-26 13:11 ` Andrew Stubbs
2014-11-27 17:28 ` Mike Stump
2014-11-27 19:29 ` Andrew Stubbs
2014-11-28 8:42 ` Mike Stump [this message]
2014-12-02 14:01 ` Kyrill Tkachov
2014-12-02 21:45 ` Ramana Radhakrishnan
2014-12-03 15:03 ` Andrew Stubbs
2014-12-23 17:32 ` Andrew Stubbs
2015-01-12 14:14 ` Andrew Stubbs
2015-01-12 14:27 ` Ramana Radhakrishnan
2015-01-13 21:08 ` Andrew Stubbs
2015-01-14 9:06 ` Ramana Radhakrishnan
2015-01-14 15:25 ` Andrew Stubbs
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=A16F5D6F-B1D1-4EAA-9D2B-5FC65F98EC84@comcast.net \
--to=mikestump@comcast.net \
--cc=James.Greenhalgh@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=ams@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jiong.wang@arm.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).