public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Charles Baylis <charles.baylis@linaro.org>
To: GCC Patches <gcc-patches@gcc.gnu.org>
Cc: Tejas Belagod <Tejas.Belagod@arm.com>,
	Alan Lawrence <alan.lawrence@arm.com>,
		Marcus Shawcroft <Marcus.Shawcroft@arm.com>,
	Richard Earnshaw <Richard.Earnshaw@arm.com>
Subject: Re: [PATCH] [AArch64] PR63870 Improve error messages for NEON single lane memory access intrinsics
Date: Thu, 11 Jun 2015 07:20:00 -0000	[thread overview]
Message-ID: <CADnVucCb07-dc9B9rbnKTZ_wUk+uW11ug7-n6Ts6JYM26+jHsQ@mail.gmail.com> (raw)
In-Reply-To: <CADnVucBF-Oc3mzsRxNzFkbqH5rvc8QNJBjZNvF9UD5QQ9tMPVw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 480 bytes --]

[resending, as previous version was rejected from the list for html]

On 11 June 2015 at 00:38, Charles Baylis <charles.baylis@linaro.org> wrote:
>
>
> On 8 June 2015 at 10:44, Alan Lawrence <alan.lawrence@arm.com> wrote:
>> Oh, have you tested bigendian?
>
> No regressions on aarch64_be-none-elf.
>
> I re-spinned the patch with the cosmetic changes Alan suggested (comment
> punctuation, fix >80 column lines in test cases)
>
> ChangeLog remains as before.
>
> Ok for trunk?
>

[-- Attachment #2: 0001-AArch64-PR63870-Improve-error-messages-for-NEON-sing.patch --]
[-- Type: application/x-download, Size: 145839 bytes --]

  parent reply	other threads:[~2015-06-10 23:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-05 17:18 Charles Baylis
2015-06-08  9:44 ` Alan Lawrence
2015-06-10  9:35   ` Charles Baylis
2015-06-10 13:01     ` Alan Lawrence
2015-06-08 10:08 ` Alan Lawrence
     [not found]   ` <CADnVucBF-Oc3mzsRxNzFkbqH5rvc8QNJBjZNvF9UD5QQ9tMPVw@mail.gmail.com>
2015-06-11  7:20     ` Charles Baylis [this message]
2015-06-17 14:15       ` Charles Baylis
2015-06-17 16:06         ` Alan Lawrence

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=CADnVucCb07-dc9B9rbnKTZ_wUk+uW11ug7-n6Ts6JYM26+jHsQ@mail.gmail.com \
    --to=charles.baylis@linaro.org \
    --cc=Marcus.Shawcroft@arm.com \
    --cc=Richard.Earnshaw@arm.com \
    --cc=Tejas.Belagod@arm.com \
    --cc=alan.lawrence@arm.com \
    --cc=gcc-patches@gcc.gnu.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).