From: Jim Wilson <jim.wilson@linaro.org>
To: Andrew Pinski <pinskia@gmail.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Jim Wilson <wilson@tuliptree.org>
Subject: Re: [PATCH, AArch64] Disable reg offset in quad-word store for Falkor.
Date: Fri, 22 Sep 2017 18:39:00 -0000 [thread overview]
Message-ID: <CABXYE2X-FfdteB-usOfeDx8Oub66KQidP55qiX=eKzTE8-5x2w@mail.gmail.com> (raw)
In-Reply-To: <CA+=Sn1=Noh74J+Y0j40GRxT9ZBCr+6UeTr3biftfdgaG96hXmg@mail.gmail.com>
On Fri, Sep 22, 2017 at 10:58 AM, Andrew Pinski <pinskia@gmail.com> wrote:
> Two overall comments:
> * What about splitting register_offset into two different elements,
> one for non 128bit modes and one for 128bit (and more; OI, etc.) modes
> so you get better address generation right away for the simd load
> cases rather than having LRA/reload having to reload the address into
> a register.
I'm not sure if changing register_offset cost would make a difference,
since costs are usually used during optimization, not during address
generation. This is something that I didn't think to try though. I
can try taking a look at this.
I did try writing a patch to modify predicates to disallow reg offset
for 128bit modes, and that got complicated, as I had to split apart a
number of patterns in the aarch64-simd.md file that accept both VD and
VQ modes. I ended up with a patch 3-4 times as big as the one I
submitted, without any additional performance improvement, so it
wasn't worth the trouble.
> * Maybe adding a testcase to the testsuite to show this change.
Yes, I can add a testcase.
> One extra comment:
> * should we change the generic tuning to avoid reg+reg for 128bit modes?
Are there other targets with a similar problem? I only know that it
is a problem for Falkor. It might be a loss for some targets as it is
replacing one instruction with two.
Jim
next prev parent reply other threads:[~2017-09-22 18:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-22 15:49 Jim Wilson
2017-09-22 15:59 ` Jim Wilson
2017-09-22 17:59 ` Andrew Pinski
2017-09-22 18:39 ` Jim Wilson [this message]
2017-09-22 21:11 ` Andrew Pinski
2017-10-12 21:54 ` Jim Wilson
2017-10-31 3:40 ` Kugan Vivekanandarajah
2017-10-31 16:18 ` Jim Wilson
2017-11-01 22:59 ` Kugan Vivekanandarajah
2017-09-22 20:06 Wilco Dijkstra
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='CABXYE2X-FfdteB-usOfeDx8Oub66KQidP55qiX=eKzTE8-5x2w@mail.gmail.com' \
--to=jim.wilson@linaro.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=pinskia@gmail.com \
--cc=wilson@tuliptree.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).