From: Jeff Law <law@redhat.com>
To: Bin Cheng <Bin.Cheng@arm.com>, "Bin.Cheng" <amker.cheng@gmail.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>, nd <nd@arm.com>
Subject: Re: [PATCH PR69052]Check if loop inv can be propagated into mem ref with additional addr expr canonicalization
Date: Fri, 19 Feb 2016 22:24:00 -0000 [thread overview]
Message-ID: <56C7962A.4010508@redhat.com> (raw)
In-Reply-To: <VI1PR08MB0512E385355AD7F24BF1497EE7AD0@VI1PR08MB0512.eurprd08.prod.outlook.com>
On 02/16/2016 11:43 AM, Bin Cheng wrote:
> ________________________________________
> From: Jeff Law <law@redhat.com>
> Sent: 11 February 2016 23:26
> To: Bin.Cheng
> Cc: Bin Cheng; gcc-patches@gcc.gnu.org; nd
> Subject: Re: [PATCH PR69052]Check if loop inv can be propagated into mem ref with additional addr expr canonicalization
>
>>> On 02/11/2016 10:59 AM, Bin.Cheng wrote:
>
>>> Hi Jeff,
>>> Thanks for detailed review. I also think a generic canonical
>>> interface for RTL is much better. I will give it a try. But with
>>> high chance it's a next stage1 stuff.
>> That is, of course, fine. However, if you do get something ready, I'd
>> support using it within LICM for gcc-6, then using it in other places
>> for gcc-7.
> Hi,
> This is the updated version patch. It fixes the problem by introducing a generic address canonicalization interface. This new interface canonicalizes address expression in following steps:
> 1) Rewrite ASHIFT into MULT recursively.
> 2) Divide address into sub expressions with PLUS as the separator.
> 3) Sort sub expressions according to precedence defined for communative operations.
> 4) Simplify CONST_INT_P sub expressions.
> 5) Create new canonicalized address and return.
>
> According to review comments, this interface is now restricted in LCIM, and will probably be expanded to other passes like fwprop and combine after entering GCC7.
> Bootstrap and test on x86_64 and AArch64. Is it OK?
>
> Thanks,
> bin
>
> 2016-02-15 Bin Cheng <bin.cheng@arm.com>
>
> PR tree-optimization/69052
> * loop-invariant.c (canonicalize_address_mult): New function.
> (MAX_CANON_ADDR_PARTS): New macro.
> (collect_address_parts): New function.
> (compare_address_parts, canonicalize_address): New functions.
> (inv_can_prop_to_addr_use): Check validity of address expression
> which is canonicalized by above canonicalize_address.
>
> gcc/testsuite/ChangeLog
> 2016-02-15 Bin Cheng <bin.cheng@arm.com>
>
> PR tree-optimization/69052
> * gcc.target/i386/pr69052.c: New test.
This is exactly what I was looking for from a design standpoint.
My only question is why didn't you use FOR_EACH_SUBRTX_VRA from
rtl-iter.h to walk the RTX expressions in collect_address_parts and
canonicalize_address_mult?
Jeff
>
>>
>> Jeff
>
next prev parent reply other threads:[~2016-02-19 22:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-09 11:08 Bin Cheng
2016-02-11 7:14 ` Jeff Law
2016-02-11 17:59 ` Bin.Cheng
2016-02-11 23:26 ` Jeff Law
2016-02-16 18:43 ` Bin Cheng
2016-02-19 22:24 ` Jeff Law [this message]
2016-02-22 9:22 ` Bin.Cheng
2016-02-25 6:39 ` Jeff Law
2016-02-25 8:47 ` Bin.Cheng
2016-03-01 17:08 ` Bin.Cheng
2016-03-01 23:44 ` Jeff Law
2016-02-23 15:10 ` Bin.Cheng
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=56C7962A.4010508@redhat.com \
--to=law@redhat.com \
--cc=Bin.Cheng@arm.com \
--cc=amker.cheng@gmail.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).