public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/45522] VRP misses oppurtunity for statement folding.
Date: Sat, 04 Sep 2010 14:11:00 -0000	[thread overview]
Message-ID: <20100904141139.21843.qmail@sourceware.org> (raw)
In-Reply-To: <bug-45522-176@http.gcc.gnu.org/bugzilla/>



------- Comment #10 from rguenther at suse dot de  2010-09-04 14:11 -------
Subject: Re:  VRP misses oppurtunity for statement
 folding.

On Sat, 4 Sep 2010, hubicka at gcc dot gnu dot org wrote:

> ------- Comment #9 from hubicka at gcc dot gnu dot org  2010-09-04 13:51 -------
> Hi,
> thanks.  In meantime I made tree-ssa-pre to fold statements it produces and it
> gets me to bootstrapland with sanity check in expr.c except for Ada (with the
> patches I sent so far)

Well - that's a workaround and will cause us to miss PRE because we do
not fold during translation of expressions.  So I wouldn't go down that
route.

> So it seems that I need to basically duplicate all logic for initializer
> folding from tree-ssa-ccp.c into this function, right? I guess it makes sense,
> but it is all quite ugly.

Yes ;)

> On VN side, i wondered if we can retire more of expand this way. For example
> dojump knows that:
> a = b ror x;
> if (a != 0)
> can be folded into:
> if (b != 0)
> (ror is rotation).  I guess we should do this kind of tricks in VN instead?

Well ... it's not that easy (that's not CSE but tree-combining, so
the specific thing would fit to forwprop).

Richard.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45522


  parent reply	other threads:[~2010-09-04 14:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-03 15:58 [Bug tree-optimization/45522] New: " hubicka at gcc dot gnu dot org
2010-09-03 15:59 ` [Bug tree-optimization/45522] " hubicka at gcc dot gnu dot org
2010-09-03 16:33 ` hubicka at gcc dot gnu dot org
2010-09-03 16:34 ` hubicka at gcc dot gnu dot org
2010-09-03 20:05 ` hubicka at gcc dot gnu dot org
2010-09-03 20:10 ` hubicka at gcc dot gnu dot org
2010-09-03 20:13 ` hubicka at gcc dot gnu dot org
2010-09-03 20:29 ` hubicka at gcc dot gnu dot org
2010-09-04  8:29 ` rguenther at suse dot de
2010-09-04 13:52 ` hubicka at gcc dot gnu dot org
2010-09-04 14:11 ` rguenther at suse dot de [this message]
2010-09-04 18:01 ` hubicka at gcc dot gnu dot org
     [not found] <bug-45522-4@http.gcc.gnu.org/bugzilla/>
2010-10-28 20:41 ` pinskia at gcc dot gnu.org

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=20100904141139.21843.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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).