From: Nigel Stephens <nigel@mips.com>
To: drow@false.org
Cc: gdb-patches@sourceware.org, Chris Dearman <chris@mips.com>,
"Maciej W. Rozycki" <macro@linux-mips.org>
Subject: Re: MIPS: Handle the DSP registers
Date: Tue, 18 Dec 2007 13:56:00 -0000 [thread overview]
Message-ID: <4767CE18.3050307@mips.com> (raw)
In-Reply-To: <20071218004304.GA29420@caradoc.them.org>
Daniel Jacobowitz wrote:
>
>
>> Index: binutils-quilt/src/gdb/features/mips-linux.xml
>> ===================================================================
>> --- binutils-quilt.orig/src/gdb/features/mips-linux.xml 2007-12-07 15:08:21.000000000 +0000
>> +++ binutils-quilt/src/gdb/features/mips-linux.xml 2007-12-07 15:13:02.000000000 +0000
>> @@ -11,6 +11,7 @@
>> <xi:include href="mips-cpu.xml"/>
>> <xi:include href="mips-cp0.xml"/>
>> <xi:include href="mips-fpu.xml"/>
>> + <xi:include href="mips-dsp.xml"/>
>>
>
> And a corrolary of that is that we'll have two mips-linux
> descriptions, with and without the DSP registers.
>
Sounds like this mechanism could rapidly get unwieldy if there were many
disjoint, optional register sets supported by an architecture -- would
you need a different description for each possible permutation? For
example with a bare-iron target you might want to omit the
floating-point register descriptions for CPUs which don't have a h/w
FPU, so then we've got Base, Base+FPU, Base+DSP, Base+FPU+DSP. Then
double again for 32-bit vs 64-bit, and so on. Or have I missed something.
Nigel
next prev parent reply other threads:[~2007-12-18 13:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-10 16:33 Maciej W. Rozycki
2007-12-18 13:42 ` Daniel Jacobowitz
2007-12-18 13:56 ` Nigel Stephens [this message]
2007-12-18 15:15 ` Daniel Jacobowitz
2007-12-18 16:06 ` Nigel Stephens
2008-03-19 17:07 ` Maciej W. Rozycki
2008-03-21 18:44 ` Daniel Jacobowitz
2008-03-26 16:59 ` Maciej W. Rozycki
2008-03-26 17:59 ` Daniel Jacobowitz
2008-03-27 17:13 ` Maciej W. Rozycki
2008-03-27 17:46 ` Daniel Jacobowitz
2008-03-28 17:16 ` Maciej W. Rozycki
2008-03-31 10:50 ` Maciej W. Rozycki
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=4767CE18.3050307@mips.com \
--to=nigel@mips.com \
--cc=chris@mips.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=macro@linux-mips.org \
/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