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/61607] DOM missed jump threading and destroyed loops
Date: Fri, 27 Jun 2014 06:21:00 -0000 [thread overview]
Message-ID: <bug-61607-4-D8RtJPY9EE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61607-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61607
Jeffrey A. Law <law at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |law at redhat dot com
--- Comment #7 from Jeffrey A. Law <law at redhat dot com> ---
In my testing, the missed thread is due to not following the chain of
SSA_NAME_VALUEs. We ought to easily discover that the two conditionals outside
the loop are in fact equivalent and fully threadable.
With a quick hack to follow the chain of values we're able to trivially
discover both of the interesting jump threading opportunities:
k.c.079t.dom1: Registering jump thread: (6, 7) incoming edge; (7, 8) normal;
k.c.079t.dom1: Registering jump thread: (5, 7) incoming edge; (7, 9) normal;
next prev parent reply other threads:[~2014-06-27 6:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-61607-4@http.gcc.gnu.org/bugzilla/>
2014-06-25 11:59 ` rguenth at gcc dot gnu.org
2014-06-25 12:10 ` rguenth at gcc dot gnu.org
2014-06-25 12:43 ` rguenth at gcc dot gnu.org
2014-06-26 7:44 ` rguenth at gcc dot gnu.org
2014-06-26 11:30 ` rguenth at gcc dot gnu.org
2014-06-26 11:55 ` rguenth at gcc dot gnu.org
2014-06-27 6:21 ` law at redhat dot com [this message]
2014-06-27 18:56 ` law at redhat dot com
2014-06-30 6:57 ` law at redhat dot com
2015-03-05 14:28 ` yroux 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=bug-61607-4-D8RtJPY9EE@http.gcc.gnu.org/bugzilla/ \
--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).