From: Charles Baylis <charles.baylis@linaro.org>
To: Alan Lawrence <alan.lawrence@arm.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
Tejas Belagod <Tejas.Belagod@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: Wed, 10 Jun 2015 09:35:00 -0000 [thread overview]
Message-ID: <CADnVucCDehNbrj2hk9RuKv6Bjykt1FUBwN-fkyUWGrJkKwvDtg@mail.gmail.com> (raw)
In-Reply-To: <5575615E.30509@arm.com>
On 8 June 2015 at 10:33, Alan Lawrence <alan.lawrence@arm.com> wrote:
> Thanks for working on this!
>
> I'd been fiddling around with a patch with some similar elements to this,
> but many trials with union types, subregs, etc., all worsened the register
> allocation and led to more unnecessary shuffling / moves.
Kugan has been looking into this at Linaro. We should avoid
duplicating effort here.
> The only real
> thing I tried which you don't do here, was to introduce a set_dreg expander
> to clean up some of those macro definitions in arm_neon.h. That could easily
> follow in a separate patch if desired!
I'd prefer that to be a separate step.
> So your patch looks good to me.
>
> A couple of style nits:
>
> --- a/gcc/config/aarch64/aarch64-builtins.c
> +++ b/gcc/config/aarch64/aarch64-builtins.c
> @@ -128,7 +128,9 @@ enum aarch64_type_qualifiers
> /* Polynomial types. */
> qualifier_poly = 0x100,
> /* Lane indices - must be in range, and flipped for bigendian. */
> - qualifier_lane_index = 0x200
> + qualifier_lane_index = 0x200,
> + /* Lane indices for single lane structure loads and stores */
> + qualifier_struct_load_store_lane_index = 0x400
> };
>
> should be ...'loads and stores. */'
>
> also the dg-error messages in the testsuite, do not need to be on the same
> line as the statement generating the error, because the trailing 0 tells dg
> that the position/line number doesn't matter (i.e. dg should allow the error
> to be reported at any line); so these could be brought under 80 chars.
OK, thanks. I'll re-spin once I've tested on big endian.
> Oh, have you tested bigendian?
I have started a bigendian build on our validation infrastructure here.
Thanks for the review
Charles
next prev parent reply other threads:[~2015-06-10 9:13 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 [this message]
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
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=CADnVucCDehNbrj2hk9RuKv6Bjykt1FUBwN-fkyUWGrJkKwvDtg@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).