public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/23855] loop header should also be pulled out of the inner loop too
Date: Thu, 20 Oct 2011 07:44:00 -0000	[thread overview]
Message-ID: <bug-23855-4-hxRJNDfOwW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-23855-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #24 from rguenther at suse dot de <rguenther at suse dot de> 2011-10-20 07:43:44 UTC ---
On Wed, 19 Oct 2011, pinskia at gcc dot gnu.org wrote:

> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23855
> 
> --- Comment #23 from Andrew Pinski <pinskia at gcc dot gnu.org> 2011-10-19 19:10:38 UTC ---
> The other way to handle this is to allow unswitch loops to handle non inner
> loops which from what I can tell is a two line patch.

Though unswitching is too late for loop invariant motion to work here.


  parent reply	other threads:[~2011-10-20  7:44 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-23855-4@http.gcc.gnu.org/bugzilla/>
2011-10-19 19:11 ` pinskia at gcc dot gnu.org
2011-10-20  7:44 ` rguenther at suse dot de [this message]
2012-12-07 10:13 ` rguenth at gcc dot gnu.org
2014-02-05 14:13 ` rguenth at gcc dot gnu.org
2014-02-05 14:14 ` rguenth at gcc dot gnu.org
2014-02-05 14:27 ` rguenth at gcc dot gnu.org
2021-07-26  3:36 ` pinskia at gcc dot gnu.org
     [not found] <bug-23855-10053@http.gcc.gnu.org/bugzilla/>
2006-01-15 20:08 ` pinskia at gcc dot gnu dot org
2006-01-15 20:12 ` pinskia at gcc dot gnu dot org
2006-01-15 20:15 ` rakdver at gcc dot gnu dot org
2006-01-17 22:28 ` rakdver at gcc dot gnu dot org
2006-01-20 23:57 ` rakdver at gcc dot gnu dot org
2006-02-28 18:23 ` patchapp at dberlin dot org
2006-04-07 11:35 ` rguenth at gcc dot gnu dot org
2006-04-07 12:01 ` rguenth at gcc dot gnu dot org
2006-04-07 12:57 ` rakdver at atrey dot karlin dot mff dot cuni dot cz
2006-04-07 13:20 ` rakdver at gcc dot gnu dot org
2006-04-09 23:51 ` rakdver at gcc dot gnu dot org
2006-04-10  0:04 ` rakdver at gcc dot gnu dot org
2006-04-10  8:11 ` rguenther at suse dot de
2006-04-10 10:24 ` rakdver at atrey dot karlin dot mff dot cuni dot cz
2006-04-10 11:56 ` rguenth at gcc dot gnu dot org
2006-10-24 13:56 ` rguenth at gcc dot gnu dot org
2006-10-24 13:59 ` rakdver at gcc dot gnu dot org
2006-10-24 14:23 ` dberlin 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=bug-23855-4-hxRJNDfOwW@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).