public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "amacleod at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/27986] [4.0/4.1/4.2 Regression] jump to middle of loop on entry with using old version of an variable
Date: Mon, 02 Oct 2006 22:14:00 -0000	[thread overview]
Message-ID: <20061002221355.1779.qmail@sourceware.org> (raw)
In-Reply-To: <bug-27986-5748@http.gcc.gnu.org/bugzilla/>



------- Comment #7 from amacleod at redhat dot com  2006-10-02 22:13 -------
Its not that you are expecting too much, just in the wrong place from my point
of view :-)  Changing the out of ssa algorithm or implementation isnt going to
change this code. It requires changing the code out of ssa sees.  

insert_backedge_copies() ought to be its own pass as well, as far as Im
concerned. Its the very first thing called, and is not related to the rest of
what out of ssa does at all.  

It should be moved out, and we can have an optimization pass just before
out-of-ssa which looks for this kind of thing.  That can happen when I start
adding the pre-passes for register pressure work if no one does it earlier.


-- 


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


  parent reply	other threads:[~2006-10-02 22:14 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-10 22:32 [Bug pending/27986] New: unnecessary jump to middle of loop on entry dean at arctic dot org
2006-06-11  8:35 ` [Bug middle-end/27986] jump to middle of loop on entry with using old version of an variable pinskia at gcc dot gnu dot org
2006-09-03  7:19 ` [Bug middle-end/27986] [4.0/4.1/4.2 Regression] " pinskia at gcc dot gnu dot org
2006-09-07  1:14 ` mmitchel at gcc dot gnu dot org
2006-09-30  9:25 ` steven at gcc dot gnu dot org
2006-10-02 13:56 ` amacleod at redhat dot com
2006-10-02 14:01 ` amacleod at redhat dot com
2006-10-02 21:46 ` steven at gcc dot gnu dot org
2006-10-02 22:14 ` amacleod at redhat dot com [this message]
2007-02-03 17:36 ` [Bug middle-end/27986] [4.0/4.1/4.2/4.3 " gdr at gcc dot gnu dot org
2007-02-03 20:42 ` pinskia at gcc dot gnu dot org
2007-02-14  9:12 ` mmitchel at gcc dot gnu dot org
2007-03-10  1:41 ` mmitchel at gcc dot gnu dot org
2008-02-19  6:01 ` xinliangli at gmail dot com
2008-02-19 17:43 ` [Bug middle-end/27986] [4.0/4.1/4.2/4.3/4.4 " dean at arctic dot org
2008-07-04 21:23 ` [Bug middle-end/27986] [4.2/4.3/4.4 " jsm28 at gcc dot gnu dot org
2009-02-12 13:59 ` [Bug middle-end/27986] [4.2 " ubizjak at gmail dot com
2009-03-30 16:58 ` jsm28 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=20061002221355.1779.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).