public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Michael Matz <matz@suse.de>
To: Rask Ingemann Lambertsen <rask@sygehus.dk>
Cc: Jan Hubicka <jh@suse.cz>, gcc-patches@gcc.gnu.org
Subject: Re: Reduce startup cost of compiler (patch 2)
Date: Fri, 03 Aug 2007 12:13:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.64.0708031408180.23011@wotan.suse.de> (raw)
In-Reply-To: <20070803091636.GM25795@sygehus.dk>

Hi,

On Fri, 3 Aug 2007, Rask Ingemann Lambertsen wrote:

> On Tue, Jul 31, 2007 at 05:44:49PM +0200, Jan Hubicka wrote:
> 
> > Well, regclass is not able to work out all details (it always assumes
> > worst case for union classes), but in your case it seems you got
> > something wrong.
> > ALL_REGS even if it contains hard regs such as stack pointers and
> > virtual frame pointers, they are fixed and should not cause much harm to
> > you. Can you send a bit more details how your classes/costs are set up?
> 
>    The comment I have for REGISTER_MOVE_COST says: "Discourage regclass.c
> from using ALL_REGS as alternate class." So the issue is not about ALL_REGS
> as the preferred class but that regclass would choose e.g. GENERAL_REGS as
> preferred class and ALL_REGS as alternate class where it should choose MEM
> as alternate class.

Well, the question was why do you think it was bad for regclass to choose 
ALL_REGS as alternate class?  It may have been not optimal perhaps, but 
from the thread it sounds as if it was a correctness issue for you.  If 
that is the case then this means you have a real bug somewhere else, as 
regclass theoretically could choose random classes as preferred and 
alternate class, and everything still works (with many reloads).  It's 
only an optimization hint, not a correctness measure.

OTOH if it was really only about optimization (i.e. choosing ALL_REGS is 
a bad decision) then adjusting the move cost was correct, but you didn't 
really have to use 65535 :-)  It would have been enough to make the cost 
higher than for memory moves.


Ciao,
Michael.

  reply	other threads:[~2007-08-03 12:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-24  5:54 Jan Hubicka
2007-07-24  7:29 ` Richard Guenther
2007-07-24  7:52   ` Paolo Bonzini
2007-07-24 15:14     ` Jan Hubicka
2007-07-29 21:32 ` Rask Ingemann Lambertsen
2007-07-31  6:44   ` Jan Hubicka
2007-07-31 12:49     ` Rask Ingemann Lambertsen
2007-07-31 16:26       ` Jan Hubicka
2007-08-03  9:16         ` Rask Ingemann Lambertsen
2007-08-03 12:13           ` Michael Matz [this message]
2007-08-03 12:43             ` Rask Ingemann Lambertsen

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=Pine.LNX.4.64.0708031408180.23011@wotan.suse.de \
    --to=matz@suse.de \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jh@suse.cz \
    --cc=rask@sygehus.dk \
    /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).