public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "steven at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/20969] unrolling does not take target register pressure into account.
Date: Thu, 04 Aug 2005 13:10:00 -0000	[thread overview]
Message-ID: <20050804131031.11601.qmail@sourceware.org> (raw)
In-Reply-To: <20050412154215.20969.amylaar@gcc.gnu.org>


------- Additional Comments From steven at gcc dot gnu dot org  2005-08-04 13:10 -------
Strength reduction already happens before loop unrolling, but I guess 
there could still be new opportunities after loop unrolling.  Not sure 
how significant that would be. 
 
For the number of loop iterations, the plan was always that loops would 
be preserved down from the tree level, and that the number of iterations 
would be computed there.  This hasn't happened yet, sadly. 
 

-- 


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


  parent reply	other threads:[~2005-08-04 13:10 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-12 15:42 [Bug rtl-optimization/20969] New: " amylaar at gcc dot gnu dot org
2005-04-12 15:49 ` [Bug rtl-optimization/20969] " cvs-commit at gcc dot gnu dot org
2005-04-12 15:50 ` cvs-commit at gcc dot gnu dot org
2005-04-12 16:02 ` pinskia at gcc dot gnu dot org
2005-04-12 16:11 ` amylaar at gcc dot gnu dot org
2005-04-12 16:14 ` amylaar at gcc dot gnu dot org
2005-04-12 16:19   ` Andrew Pinski
2005-04-12 16:20 ` pinskia at physics dot uc dot edu
2005-04-12 16:26 ` pinskia at gcc dot gnu dot org
2005-04-12 17:21 ` amylaar at gcc dot gnu dot org
2005-04-12 17:24 ` pinskia at gcc dot gnu dot org
2005-04-12 17:42 ` pinskia at gcc dot gnu dot org
2005-04-12 17:48 ` amylaar at gcc dot gnu dot org
2005-07-28 16:21 ` steven at gcc dot gnu dot org
2005-08-03 15:49 ` steven at gcc dot gnu dot org
2005-08-04 12:14 ` joern dot rennecke at st dot com
2005-08-04 13:10 ` steven at gcc dot gnu dot org [this message]
2005-08-04 13:37 ` amylaar 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=20050804131031.11601.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).