From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: stupify MAX_REGISTER_{RAW,VIRTUAL}_SIZE
Date: Wed, 02 Apr 2003 00:20:00 -0000 [thread overview]
Message-ID: <20030402002038.GA16136@nevyn.them.org> (raw)
In-Reply-To: <3E8A2B34.3080504@redhat.com>
On Tue, Apr 01, 2003 at 07:13:40PM -0500, Andrew Cagney wrote:
> Hmm,
>
> The architecture vector contains the two macros:
>
> MAX_REGISTER_RAW_SIZE
> MAX_REGISTER_VIRTUAL_SIZE
>
> which provide small per-architecture upper bounds on a register. They
> are used when allocating scratch buffers (typically using alloca()).
> The regcache provides a successor - max_register_size().
>
> I'm now wondering if it would be easier to simply define:
>
> enum { MAX_REGISTER_SIZE = 16 };
>
> and then, if that ever proves to be too small, make it bigger. Just as
> long as no one creates an architecture with >~2k registers ....
Entirely in favor!
I've got a port which supports 20, and we'll probably be seeing 32 in
new platforms soon - but I don't think using a constant will get out of
hand for a long time.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2003-04-02 0:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-02 0:13 Andrew Cagney
2003-04-02 0:20 ` Daniel Jacobowitz [this message]
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=20030402002038.GA16136@nevyn.them.org \
--to=drow@mvista.com \
--cc=ac131313@redhat.com \
--cc=gdb@sources.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