From: Christophe Lyon <christophe.lyon@linaro.org>
To: "Richard Earnshaw (lists)" <Richard.Earnshaw@arm.com>
Cc: Wilco Dijkstra <Wilco.Dijkstra@arm.com>,
GCC Patches <gcc-patches@gcc.gnu.org>, nd <nd@arm.com>
Subject: Re: [PATCH][AArch64] Improve legitimize_address
Date: Wed, 07 Sep 2016 20:04:00 -0000 [thread overview]
Message-ID: <CAKdteOYt3q7+sc2Gp9c50gdkiemvs1uh1sbk7SSmL1M4aSOvbQ@mail.gmail.com> (raw)
In-Reply-To: <d73a03df-6ce5-19ed-ee67-9e45fdb234d8@arm.com>
Hi Wilco,
On 7 September 2016 at 14:43, Richard Earnshaw (lists)
<Richard.Earnshaw@arm.com> wrote:
> On 06/09/16 14:14, Wilco Dijkstra wrote:
>> Improve aarch64_legitimize_address - avoid splitting the offset if it is
>> supported. When we do split, take the mode size into account. BLKmode
>> falls into the unaligned case but should be treated like LDP/STP.
>> This improves codesize slightly due to fewer base address calculations:
>>
>> int f(int *p) { return p[5000] + p[7000]; }
>>
>> Now generates:
>>
>> f:
>> add x0, x0, 16384
>> ldr w1, [x0, 3616]
>> ldr w0, [x0, 11616]
>> add w0, w1, w0
>> ret
>>
>> instead of:
>>
>> f:
>> add x1, x0, 16384
>> add x0, x0, 24576
>> ldr w1, [x1, 3616]
>> ldr w0, [x0, 3424]
>> add w0, w1, w0
>> ret
>>
>> OK for trunk?
>>
>> ChangeLog:
>> 2016-09-06 Wilco Dijkstra <wdijkstr@arm.com>
>>
>> gcc/
>> * config/aarch64/aarch64.c (aarch64_legitimize_address):
>> Avoid use of base_offset if offset already in range.
>
> OK.
>
> R.
After this patch, I've noticed a regression:
FAIL: gcc.target/aarch64/ldp_vec_64_1.c scan-assembler ldp\td[0-9]+, d[0-9]
You probably need to adjust the scan pattern.
Thanks,
Christophe
>
>> --
>>
>> diff --git a/gcc/config/aarch64/aarch64.c b/gcc/config/aarch64/aarch64.c
>> index 27bbdbad8cddc576f9ed4fd0670116bd6d318412..119ff0aecb0c9f88899fa141b2c7f9158281f9c3 100644
>> --- a/gcc/config/aarch64/aarch64.c
>> +++ b/gcc/config/aarch64/aarch64.c
>> @@ -5058,9 +5058,19 @@ aarch64_legitimize_address (rtx x, rtx /* orig_x */, machine_mode mode)
>> /* For offsets aren't a multiple of the access size, the limit is
>> -256...255. */
>> else if (offset & (GET_MODE_SIZE (mode) - 1))
>> - base_offset = (offset + 0x100) & ~0x1ff;
>> + {
>> + base_offset = (offset + 0x100) & ~0x1ff;
>> +
>> + /* BLKmode typically uses LDP of X-registers. */
>> + if (mode == BLKmode)
>> + base_offset = (offset + 512) & ~0x3ff;
>> + }
>> + /* Small negative offsets are supported. */
>> + else if (IN_RANGE (offset, -256, 0))
>> + base_offset = 0;
>> + /* Use 12-bit offset by access size. */
>> else
>> - base_offset = offset & ~0xfff;
>> + base_offset = offset & (~0xfff * GET_MODE_SIZE (mode));
>>
>> if (base_offset != 0)
>> {
>>
>
next prev parent reply other threads:[~2016-09-07 19:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-06 13:31 Wilco Dijkstra
2016-09-07 12:59 ` Richard Earnshaw (lists)
2016-09-07 20:04 ` Christophe Lyon [this message]
2016-09-08 11:56 ` 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=CAKdteOYt3q7+sc2Gp9c50gdkiemvs1uh1sbk7SSmL1M4aSOvbQ@mail.gmail.com \
--to=christophe.lyon@linaro.org \
--cc=Richard.Earnshaw@arm.com \
--cc=Wilco.Dijkstra@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=nd@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).