From: Rask Ingemann Lambertsen <rask@sygehus.dk>
To: Jan Hubicka <jh@suse.cz>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: Reduce startup cost of compiler (patch 2)
Date: Sun, 29 Jul 2007 21:32:00 -0000 [thread overview]
Message-ID: <20070729203752.GH25795@sygehus.dk> (raw)
In-Reply-To: <20070724050210.GC10270@kam.mff.cuni.cz>
On Tue, Jul 24, 2007 at 07:02:10AM +0200, Jan Hubicka wrote:
> Index: regclass.c
[snip init_move_cost()]
> + cost = REGISTER_MOVE_COST (m, i, j);
> + gcc_assert (cost < 65535);
Would you mind documenting this new upper limit? It happened to break my
16-bit x86 target where I try to discurage the register allocator from using
unusable classes such as ALL_REGS.
--
Rask Ingemann Lambertsen
next prev parent reply other threads:[~2007-07-29 20:37 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 [this message]
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
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=20070729203752.GH25795@sygehus.dk \
--to=rask@sygehus.dk \
--cc=gcc-patches@gcc.gnu.org \
--cc=jh@suse.cz \
/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).