From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: Re: [rfc] Target-described register support for MIPS
Date: Wed, 13 Jun 2007 18:28:00 -0000 [thread overview]
Message-ID: <20070613182823.GH1023@caradoc.them.org> (raw)
In-Reply-To: <20070521133939.GA8161@caradoc.them.org>
On Mon, May 21, 2007 at 09:39:39AM -0400, Daniel Jacobowitz wrote:
> This patch adds target-described register support to the MIPS port, in
> basically the same way I did for ARM. The target must supply some CPU
> registers, a tiny subset of CP0, and an FPU.
I've checked it in, after updating for macro removal.
--
Daniel Jacobowitz
CodeSourcery
2007-06-13 Daniel Jacobowitz <dan@codesourcery.com>
* Makefile.in (mips-tdep.o): Update.
* mips-tdep.c (struct register_alias, mips_o32_aliases)
(mips_n32_n64_aliases, mips_register_aliases): New.
(mips_register_name): Call tdesc_register_name.
(mips_tdesc_register_reggroup_p): New.
(mips_pseudo_register_type, value_of_mips_user_reg): New.
(mips_gdbarch_init): Add target-described register support.
Register aliases for register names.
* target-descriptions.c (tdesc_register_name): Make global.
(tdesc_register_in_reggroup_p): New function, broken out from
tdesc_register_reggroup_p.
(tdesc_register_reggroup_p): Use it.
* target-descriptions.h (tdesc_register_name)
(tdesc_register_in_reggroup_p): New prototypes.
* NEWS: Correct formatting. Mention MIPS register support.
* features/mips-cp0.xml, features/mips-fpu.xml,
features/mips64-cp0.xml, gdb/features/mips64-fpu.xml, mips-cpu.xml,
features/mips64-cpu.xml: New files.
* gdb.xml/tdesc-regs.exp: Add MIPS support. Allow multiple
required features to be included.
* gdb.texinfo (MIPS Features): New subsection.
prev parent reply other threads:[~2007-06-13 18:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-21 13:40 Daniel Jacobowitz
2007-06-12 18:14 ` Maciej W. Rozycki
2007-06-12 18:25 ` Daniel Jacobowitz
2007-06-13 11:42 ` Maciej W. Rozycki
2007-06-13 15:05 ` Thiemo Seufer
2007-06-13 17:37 ` Daniel Jacobowitz
2007-06-13 18:28 ` 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=20070613182823.GH1023@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.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