public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jan Hubicka <jh@suse.cz>
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: Tue, 31 Jul 2007 16:26:00 -0000	[thread overview]
Message-ID: <20070731154449.GA11467@kam.mff.cuni.cz> (raw)
In-Reply-To: <20070731121109.GU25795@sygehus.dk>

> On Tue, Jul 31, 2007 at 05:52:16AM +0200, Jan Hubicka wrote:
> > 
> > Hi,
> > the limitation was alwas there
> 
>    COSTS_N_INSNS (60000) = 240000 used to work fine. :-)

Well, it depends on definition of the word "work" :)
It a sense of not ICEing it works, in a sense of giving meaningful cost
model it does not.
> 
> > - regclass used value of 65535 as an
> > infinity for impossible combinations.  This also means that you should
> > not need to discougrate ALL_REGS and similar classes since regstack is
> > supposed to work this out.
> 
>    It's a good thing you say "supposed to". Regclass tends to prefer
> ALL_REGS over MEM and ALL_REGS tends to include such things as virtual
> hard regs. Returning a high REGISTER_MOVE_COST for ALL_REGS keeps regclass
> clear of ALL_REGS.

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?
> 
> >   if the @samp{mov@var{m}} pattern's constraints do not allow such copying.
> > + The maximal allowed value is 65535.
> >   @end defmac
> 
>    Well, it's 65534, isn't it?

Hmm, if we can find good reason for register move cost to trick the
infinity cost as you want to do, we can probably relax the assert and
document 65535 as infinity.

Honza
> 
> -- 
> Rask Ingemann Lambertsen

  reply	other threads:[~2007-07-31 15:44 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 [this message]
2007-08-03  9:16         ` Rask Ingemann Lambertsen
2007-08-03 12:13           ` Michael Matz
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=20070731154449.GA11467@kam.mff.cuni.cz \
    --to=jh@suse.cz \
    --cc=gcc-patches@gcc.gnu.org \
    --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).