public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joern dot rennecke at st dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/20211] autoincrement generation is poor
Date: Mon, 28 Feb 2005 20:49:00 -0000	[thread overview]
Message-ID: <20050228134644.22017.qmail@sourceware.org> (raw)
In-Reply-To: <20050225161912.20211.amylaar@gcc.gnu.org>


------- Additional Comments From joern dot rennecke at st dot com  2005-02-28 13:46 -------
Subject: Re:  autoincrement generation is poor

giovannibajo at libero dot it wrote:

>------- Additional Comments From giovannibajo at libero dot it  2005-02-25 18:59 -------
>What is the compile-time impact of this patch on cc-i compilation, the usual 
>C++ testcases, and SPEC? I am sure this is something worthwile to mention for 
>a review.
>  
>

Sorry, I don't have such numbers at the moment.  Note that this 
optimization is specific to
AUTO_INC_DEC targets (in principle it is possible to use it to reduce 
register pressure on
other targets too, but there is also a cost to pay in reduced 
flexibility for sched2 till you make
the scheduler aware of the possible transformations).
Note that there is a specific flag to enable or disable this 
optimization, so for each target this
can be tuned by OPTIMIZATION_OPTIONS.  I made this switch default-on at 
-O2 mainly
because it makes testing the patch much simpler.  For integration, I'm 
also fine with having it
default-off and having only the targets that want it turn it on in 
OPTIMIZATION_OPTIONS.

>And BTW, out of curiosity, does the new pass have to live in regmove.c?
>  
>
Not absolutely, but it makes sense insofar as an aspect of this 
optimization is to avoid register-register
moves  which are required when you end up with awkward register 
assignments for the addds,
and it is also nice to have sched1 run first. And there is also the 
issue fo inserting add instructions,
which needs infrastructure from regmove to avoid issues with targets 
that have a flags register that
can be clobbered by the new adds.
For the c4x, it would make sense to run this pass earlier, as detailed 
in the 1999 thread.



-- 


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


  parent reply	other threads:[~2005-02-28 13:47 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-25 22:08 [Bug rtl-optimization/20211] New: " amylaar at gcc dot gnu dot org
2005-02-26  1:13 ` [Bug rtl-optimization/20211] " pinskia at gcc dot gnu dot org
2005-02-26  1:24 ` giovannibajo at libero dot it
2005-02-27  4:49 ` hp at gcc dot gnu dot org
2005-02-28 20:49 ` joern dot rennecke at st dot com [this message]
2005-03-15  2:12 ` giovannibajo at libero dot it
2005-03-15 18:08 ` amylaar at gcc dot gnu dot org
2005-03-17 16:38 ` amylaar at gcc dot gnu dot org
2005-04-12 18:06 ` amylaar at gcc dot gnu dot org
2005-04-27 13:38 ` amylaar at gcc dot gnu dot org
2005-04-27 13:42 ` pinskia at gcc dot gnu dot org
2005-04-28 13:37 ` amylaar at gcc dot gnu dot org
2005-04-28 13:43 ` pinskia at gcc dot gnu dot org
2005-04-28 19:21 ` amylaar at gcc dot gnu dot org
2005-05-12 19:00 ` pinskia at gcc dot gnu dot org
2005-05-12 19:31 ` joern dot rennecke at st dot com
2005-05-17 19:20 ` amylaar at gcc dot gnu dot org
2005-09-19 16:52 ` cvs-commit at gcc dot gnu dot org
2005-09-19 16:54 ` cvs-commit at gcc dot gnu dot org
2005-09-19 17:30 ` amylaar at gcc dot gnu dot org
     [not found] <bug-20211-5394@http.gcc.gnu.org/bugzilla/>
2005-11-02 21:50 ` amylaar at gcc dot gnu dot org
2006-11-15 20:11 ` amylaar at gcc dot gnu dot org
2006-11-30 20:05 ` amylaar at gcc dot gnu dot org
2006-12-17 14:47 ` steven at gcc dot gnu dot org
2007-06-18  2:03 ` pinskia at gcc dot gnu dot org
2007-09-17 20:06 ` rguenth at gcc dot gnu dot org
2008-05-23 23:14 ` hp at gcc dot gnu dot org
2010-02-22  6:05 ` amylaar at gcc dot gnu dot org
     [not found] <bug-20211-4@http.gcc.gnu.org/bugzilla/>
2013-12-24 22:55 ` steven at gcc dot gnu.org
2015-09-21  8:15 ` olegendo 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=20050228134644.22017.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).