public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/21417] Missed jump threading opportunity on trees
Date: Thu, 09 Feb 2006 02:36:00 -0000	[thread overview]
Message-ID: <20060209023608.25325.qmail@sourceware.org> (raw)
In-Reply-To: <bug-21417-280@http.gcc.gnu.org/bugzilla/>



------- Comment #5 from law at redhat dot com  2006-02-09 02:36 -------
Subject: Re:  Missed jump threading
        opportunity on trees

On Mon, 2006-02-06 at 16:17 +0000, pinskia at gcc dot gnu dot org wrote:
> 
> ------- Comment #3 from pinskia at gcc dot gnu dot org  2006-02-06 16:17 -------
> the load PRE issue has been fixed but DOM does not thread the jump for some
> reason.
This patch allows DOM to thread the jump in question (which in
effect pulls the conditional out of the loop, definitely a good
thing to do when we can).

As I mentioned in a previous comment, we were being very conservative
when threading across backedges in the CFG.  We can be a little more
aggressive, specifically we can allow statements in the target block
which do not affect the control statement at the end of the target
block.

This triggered a few more times in my testbucket, so I'm confident
it's allowing us to avoid conditionals in at least a few real world
hunks of code.

Bootstrapped and regression tested on i686-pc-linux-gnu.


------- Comment #6 from law at redhat dot com  2006-02-09 02:36 -------
Created an attachment (id=10812)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=10812&action=view)


-- 


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


  parent reply	other threads:[~2006-02-09  2:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-21417-280@http.gcc.gnu.org/bugzilla/>
2006-01-21  3:03 ` pinskia at gcc dot gnu dot org
2006-02-06 16:17 ` pinskia at gcc dot gnu dot org
2006-02-07 21:24 ` law at redhat dot com
2006-02-09  2:36 ` law at redhat dot com
2006-02-09  2:36 ` law at redhat dot com [this message]
2006-02-09  2:36 ` law at gcc dot gnu dot org
2005-05-06 13:11 [Bug middle-end/21417] New: " steven at gcc dot gnu dot org
2005-05-06 13:53 ` [Bug tree-optimization/21417] " pinskia at gcc dot gnu dot org
2005-05-06 14:12 ` pinskia at gcc dot gnu dot 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=20060209023608.25325.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).