public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/42646] Jump threading breaks canonical loop forms
Date: Fri, 08 Jan 2010 11:53:00 -0000	[thread overview]
Message-ID: <20100108115255.26923.qmail@sourceware.org> (raw)
In-Reply-To: <bug-42646-15392@http.gcc.gnu.org/bugzilla/>



------- Comment #4 from rguenth at gcc dot gnu dot org  2010-01-08 11:52 -------
It just means that we shouldn't thread to the header but always to the latch
block.  Note that this restriction should probably be restricted to the
threading before loop optimizations.  Or the 1st jump threading should simply
avoid to thread over backedges (equivalent to removing the 1st DOM pass -
though
there is interesting fallout regarding jump-threading / loop header copying
pass ordering).


-- 


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


  parent reply	other threads:[~2010-01-08 11:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-07 14:27 [Bug tree-optimization/42646] New: " joefoxreal at gmail dot com
2010-01-07 14:29 ` [Bug tree-optimization/42646] " joefoxreal at gmail dot com
2010-01-08  1:40 ` joefoxreal at gmail dot com
2010-01-08  1:42 ` joefoxreal at gmail dot com
2010-01-08 11:53 ` rguenth at gcc dot gnu dot org [this message]
     [not found] <bug-42646-4@http.gcc.gnu.org/bugzilla/>
2021-08-05 21:36 ` 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=20100108115255.26923.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).