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/13875] [tree-ssa] missed jump thread optimization on the tree-level
Date: Mon, 13 Jun 2005 13:52:00 -0000 [thread overview]
Message-ID: <20050613135221.1764.qmail@sourceware.org> (raw)
In-Reply-To: <20040127051055.13875.dann@godzilla.ics.uci.edu>
------- Additional Comments From law at redhat dot com 2005-06-13 13:52 -------
Subject: Re: [tree-ssa] missed jump thread
optimization on the tree-level
On Sun, 2005-06-12 at 20:41 +0000, pinskia at gcc dot gnu dot org wrote:
> ------- Additional Comments From pinskia at gcc dot gnu dot org 2005-06-12 20:41 -------
> Hmm, I have not seen any more, could you double check this?
FWIW, it is still possible to miss jump threading opportunities,
it's just a lot harder now :-)
The most common ways we miss threading opportunities are:
1. Cascading jump threading opportunities. We're more conservative
than we need to be with the iteration step. This can cause us
to miss jump threading opportunities because we're not iterating.
A great example of this would be a loop where the backedge is
always threadable. There's an example of this in one of the
testcases in the various open PRs. I'm working on resolving some
of the issues necessary to address this limitation right now.
2. We're not recording all the expressions we encounter when
attempting to thread through a basic block. ie, if we
encounter x = a + b and "a + b" does not simplify, then we
do not record anything in our hash tables for "x". It is
possible that recording the equivalence between x and a + b
can result in more threading opportunities. I believe
there is also a testcase which exposes this limitation in
one of the still open PRs.
jeff
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13875
next prev parent reply other threads:[~2005-06-13 13:52 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-27 5:11 [Bug optimization/13875] New: [tree-ssa] function not optimized dann at godzilla dot ics dot uci dot edu
2004-01-27 5:13 ` [Bug optimization/13875] " pinskia at gcc dot gnu dot org
2004-01-30 0:33 ` pinskia at gcc dot gnu dot org
2004-01-31 3:43 ` pinskia at gcc dot gnu dot org
2004-02-29 4:01 ` [Bug optimization/13875] [tree-ssa] missed jump thread optimization on the tree-level pinskia at gcc dot gnu dot org
2004-02-29 4:09 ` pinskia at gcc dot gnu dot org
2004-03-01 3:43 ` law at gcc dot gnu dot org
2004-03-01 17:52 ` law at gcc dot gnu dot org
2004-03-01 19:51 ` giovannibajo at libero dot it
2004-03-03 18:14 ` dann at godzilla dot ics dot uci dot edu
2004-03-03 18:26 ` law at redhat dot com
2004-03-08 2:07 ` law at redhat dot com
2004-03-08 2:09 ` law at gcc dot gnu dot org
2004-03-08 23:47 ` dann at godzilla dot ics dot uci dot edu
2004-03-08 23:51 ` pinskia at gcc dot gnu dot org
2004-03-09 23:37 ` law at redhat dot com
2004-04-06 1:27 ` dann at godzilla dot ics dot uci dot edu
2004-04-06 1:44 ` pinskia at gcc dot gnu dot org
2004-04-08 22:58 ` law at redhat dot com
2004-04-08 23:36 ` dann at godzilla dot ics dot uci dot edu
2004-04-08 23:45 ` law at redhat dot com
2004-04-20 16:40 ` dann at godzilla dot ics dot uci dot edu
2004-05-27 7:54 ` [Bug tree-optimization/13875] " pinskia at gcc dot gnu dot org
2004-06-02 20:16 ` pinskia at gcc dot gnu dot org
2004-10-11 17:08 ` pinskia at gcc dot gnu dot org
2005-01-15 5:38 ` pinskia at gcc dot gnu dot org
2005-06-12 20:41 ` pinskia at gcc dot gnu dot org
2005-06-13 13:52 ` law at redhat dot com [this message]
[not found] <bug-13875-1008@http.gcc.gnu.org/bugzilla/>
2007-03-29 12:19 ` steven 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=20050613135221.1764.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).