public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Zack Weinberg <zack@codesourcery.com>
To: law@redhat.com
Cc: Fergus Henderson <fjh@cs.mu.oz.au>, gcc@gcc.gnu.org
Subject: Re: The bloat sweepstakes...
Date: Mon, 22 Oct 2001 00:39:00 -0000	[thread overview]
Message-ID: <20011022003928.E3425@codesourcery.com> (raw)
In-Reply-To: <2285.1003367312@localhost.localdomain>

On Wed, Oct 17, 2001 at 07:08:32PM -0600, law@redhat.com wrote:
>   In message < 20011010150953.U9432@codesourcery.com >you write:
>   > I think costs never get higher than 10 or so;
> They certainly do get higher than 10.  Also remember that costs accumulate
> across the uses of a register.  Making them an unsigned character probably
> is not a wise idea.

The arrays that are taking up lots of space are the ones in regclass.c
(move_cost, may_move_in_cost, may_move_out_cost), and it looks to me
like they don't ever get very high.  In fact, 65536 is being used in
regclass as infinity, suggesting that it would at least be safe to
make them short.

zw

  reply	other threads:[~2001-10-22  0:39 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-07 10:25 Zack Weinberg
2001-10-07 10:44 ` guerby
2001-10-07 11:26   ` Zack Weinberg
2001-10-07 11:44     ` guerby
2001-10-07 12:43       ` Zack Weinberg
2001-10-07 14:42         ` guerby
2001-10-09 23:24 ` Fergus Henderson
2001-10-10 15:09   ` Zack Weinberg
2001-10-10 23:03     ` Fergus Henderson
2001-10-10 23:46       ` Zack Weinberg
2001-10-19  9:43     ` law
2001-10-22  0:39       ` Zack Weinberg [this message]
2001-10-22  8:28         ` law
2001-10-22 15:01           ` Richard Henderson
2001-10-07 15:16 dewar
2001-10-08  9:59 ` Zack Weinberg
2001-10-07 15:21 dewar
2001-10-07 15:24 dewar
2001-10-08 10:01 dewar
2001-10-08 10:03 dewar
2001-10-08 10:07 dewar
2001-10-08 11:04 ` Zack Weinberg

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=20011022003928.E3425@codesourcery.com \
    --to=zack@codesourcery.com \
    --cc=fjh@cs.mu.oz.au \
    --cc=gcc@gcc.gnu.org \
    --cc=law@redhat.com \
    /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).