From: "Bin.Cheng" <amker.cheng@gmail.com>
To: Richard Guenther <richard.guenther@gmail.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Missed optimization in PRE?
Date: Thu, 29 Mar 2012 10:22:00 -0000 [thread overview]
Message-ID: <CAHFci28_YcnFJ-P6-9CHHY=4CaRGr1bpo8g=m6fwNGwjMVahXw@mail.gmail.com> (raw)
In-Reply-To: <CAFiYyc1SD6vdqMYjKVPPMOMLDXo6+5YO-39qQ86+F=02ZEuQNQ@mail.gmail.com>
On Thu, Mar 29, 2012 at 6:14 PM, Richard Guenther
<richard.guenther@gmail.com> wrote:
> On Thu, Mar 29, 2012 at 12:10 PM, Bin.Cheng <amker.cheng@gmail.com> wrote:
>> On Thu, Mar 29, 2012 at 6:07 PM, Richard Guenther
>> <richard.guenther@gmail.com> wrote:
>>> On Thu, Mar 29, 2012 at 12:02 PM, Bin.Cheng <amker.cheng@gmail.com> wrote:
>>>> Hi,
>>>> Following is the tree dump of 094t.pre for a test program.
>>>> Question is loads of D.5375_12/D.5375_14 are redundant on path <bb2,
>>>> bb7, bb5, bb6>,
>>>> but why not lowered into basic block 3, where it is used.
>>>>
>>>> BTW, seems no tree pass handles this case currently.
>>>
>>> tree-ssa-sink.c should do this.
>>>
>> It does not work for me, I will double check and update soon.
>
> Well, "should" as in, it's the place to do it. And certainly the pass can sink
> loads, so this must be a missed optimization.
>
ok, I will investigate it.
--
Best Regards.
next prev parent reply other threads:[~2012-03-29 10:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-29 10:02 Bin.Cheng
2012-03-29 10:07 ` Richard Guenther
2012-03-29 10:10 ` Bin.Cheng
2012-03-29 10:14 ` Richard Guenther
2012-03-29 10:22 ` Bin.Cheng [this message]
2012-03-29 15:25 ` Bin.Cheng
2012-03-30 8:16 ` Richard Guenther
2012-03-30 9:43 ` Bin.Cheng
2012-04-09 6:00 ` Bin.Cheng
2012-04-09 11:02 ` Richard Guenther
2012-04-11 3:28 ` Bin.Cheng
2012-04-11 8:05 ` Bin.Cheng
2012-04-11 9:09 ` Richard Guenther
2012-04-11 9:25 ` Bin.Cheng
2012-04-11 10:02 ` Richard Guenther
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='CAHFci28_YcnFJ-P6-9CHHY=4CaRGr1bpo8g=m6fwNGwjMVahXw@mail.gmail.com' \
--to=amker.cheng@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=richard.guenther@gmail.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).