public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Alan Lawrence <alan.lawrence@arm.com>
To: Charles Baylis <charles.baylis@linaro.org>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
	 Kugan <kugan.vivekanandarajah@linaro.org>
Subject: Re: [PATCH] [AArch64] PR63870 Improve error messages for NEON single lane memory access intrinsics
Date: Wed, 10 Jun 2015 13:01:00 -0000	[thread overview]
Message-ID: <55782B1D.90005@arm.com> (raw)
In-Reply-To: <CADnVucCDehNbrj2hk9RuKv6Bjykt1FUBwN-fkyUWGrJkKwvDtg@mail.gmail.com>

Charles Baylis wrote:
> 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.

Yes. I stopped short of looking into the internals of the register allocator, 
although I believe any proper solution is going to have to make changes here. 
However, I am working on (/nearly finished, just some tidying!) a patch series 
to add D-registers to TARGET_ARRAY_MODE_SUPPORTED_P, which may help matters.

>> 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.

Sure. (*If* we go that route - I hope to have another look after 
aarch64_array_mode_supported_p).

Cheers,
Alan

  reply	other threads:[~2015-06-10 12:18 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 [this message]
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=55782B1D.90005@arm.com \
    --to=alan.lawrence@arm.com \
    --cc=charles.baylis@linaro.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=kugan.vivekanandarajah@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).