From: Kenneth Zadeck <zadeck@naturalbridge.com>
To: Zdenek Dvorak <rakdver@kam.mff.cuni.cz>
Cc: Kenneth Zadeck <Kenneth.Zadeck@NaturalBridge.com>,
gcc@gcc.gnu.org, rakdver@atrey.karlin.mff.cuni.cz,
dnovillo@google.com
Subject: Re: Tree-SSA and POST_INC address mode inompatible in GCC4?
Date: Sat, 03 Nov 2007 14:52:00 -0000 [thread overview]
Message-ID: <472C8B27.6080303@naturalbridge.com> (raw)
In-Reply-To: <20071103142504.GA5043@kam.mff.cuni.cz>
Zdenek Dvorak wrote:
> Hi,
>
>
>> I believe that this is something new and is most likely fallout from
>> diego's reworking of the tree to rtl converter.
>>
>> To fix this will require a round of copy propagation, most likely in
>> concert with some induction variable detection, since the most
>> profitable place for this will be in loops.
>>
>> I wonder if any of this effects the rtl level induction variable
>> discovery?
>>
>
> it should not (iv analysis is able to deal with this kind of ivs).
>
> Zdenek
>
>
does the iv analysis canonize them in a way that we should perhaps
consider moving the auto-inc detection after the iv analysis?
>>> Hi, Ramana,
>>> I tried the trunk version with/without your patch. It still produces
>>> the same code as gcc4.2.2 does. In auto-inc-dec.c, the comments say
>>>
>>> *a
>>> ...
>>> a <- a + c
>>>
>>> becomes
>>>
>>> *(a += c) post
>>>
>>> But the problem is after Tree-SSA pass, there is no
>>> a <- a + c
>>> But something like
>>> a_1 <- a + c
>>>
>>> Unless the auto-inc-dec.c can reverse a_1 <- a + c to a <- a + c. I
>>> don't see this transformation is applicable in most scenarios. Any
>>> comments?
>>>
>>> Cheers,
>>> Bingfeng
>>>
>>>
next prev parent reply other threads:[~2007-11-03 14:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-02 12:24 Bingfeng Mei
2007-11-02 12:38 ` Ramana Radhakrishnan
2007-11-02 14:34 ` Bingfeng Mei
2007-11-03 13:52 ` Kenneth Zadeck
2007-11-03 14:25 ` Zdenek Dvorak
2007-11-03 14:52 ` Kenneth Zadeck [this message]
2007-11-03 15:27 ` Zdenek Dvorak
2007-11-03 16:23 ` Bingfeng Mei
2007-11-03 16:37 ` Richard Guenther
2007-11-04 3:13 ` Daniel Berlin
2007-11-04 23:51 ` Mark Mitchell
2007-11-05 19:30 ` Paul Brook
2007-11-03 14:47 J.C. Pizarro
2007-11-03 14:55 ` Kenneth Zadeck
2007-11-03 14:59 ` J.C. Pizarro
2007-11-03 14:55 ` J.C. Pizarro
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=472C8B27.6080303@naturalbridge.com \
--to=zadeck@naturalbridge.com \
--cc=Kenneth.Zadeck@NaturalBridge.com \
--cc=dnovillo@google.com \
--cc=gcc@gcc.gnu.org \
--cc=rakdver@atrey.karlin.mff.cuni.cz \
--cc=rakdver@kam.mff.cuni.cz \
/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).