From: Fred Fish <fnf@ninemoons.com>
To: Andrew Cagney <cagney@gnu.org>, Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com, fnf@ninemoons.com
Subject: Re: [PATCH] Remove some hardwired assumptions about register sets
Date: Fri, 02 Jan 2004 23:12:00 -0000 [thread overview]
Message-ID: <200401021611.11737.fnf@ninemoons.com> (raw)
In-Reply-To: <3FF5C642.3000504@gnu.org>
> Daniel, the patch adds a global variable "num_mips_processor_regs"
We could use a new "tdep->num_mips_processor_regs" variable instead.
That is probably cleaner anyway.
> I'm wondering what motivated the change?
> ... sidestep the issue
> ... made all the arrays the same size.
The problem is the assumption that all the arrays are the same size,
or perhaps more fundamentally, that "all mips architectures will have
registers sets of similar size'.
I'm working on port, which will soon be contributed, that currently
adds 384 new register names (reg numbers 32-415) for a matrix
coprocessor (cop 2).
When contributed though the names will be reduced to just 69 new
names (32-100). The original port assigned separate register names to
each of the individual 256 matrix elements (16 vectors of 16 elements)
instead of handling each 16 element vector as a single named vector
register.
Still, even with 69 new names, it gets really ugly having all the
other *_reg_name[] arrays have to be full of mostly null strings.
-Fred
next prev parent reply other threads:[~2004-01-02 23:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-17 6:14 Fred Fish
2003-12-17 6:22 ` Fred Fish
2003-12-23 1:51 ` Fred Fish
2003-12-23 2:03 ` Daniel Jacobowitz
2004-01-02 19:28 ` Andrew Cagney
2004-01-02 19:31 ` Daniel Jacobowitz
2004-01-02 23:12 ` Fred Fish [this message]
2004-01-05 15:50 ` Andrew Cagney
2003-12-23 11:30 ` Mark Kettenis
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=200401021611.11737.fnf@ninemoons.com \
--to=fnf@ninemoons.com \
--cc=cagney@gnu.org \
--cc=drow@mvista.com \
--cc=gdb-patches@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