public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Stafford Horne <shorne@gmail.com>
To: GDB patches <gdb-patches@sourceware.org>
Cc: Stafford Horne <shorne@gmail.com>
Subject: [PATCH 0/3] Support for arbitrary reggroups
Date: Wed, 07 Jun 2017 22:15:00 -0000	[thread overview]
Message-ID: <cover.1496871270.git.shorne@gmail.com> (raw)

Traditionally registers have been limited to names like "vector",
"general", "system" which are hard coded in the gdbarch.  This patch allows
additional reggroups to be defined by the xml target description.

This is necessary for architectures like OpenRISC which have many
registers.

Stafford Horne (3):
  reggroups: Add test and docs for `info reg $reggroup` feature
  reggroups: Convert reggroups from post_init to pre_init
  tdesc: handle arbitrary strings in tdesc_register_in_reggroup_p

 gdb/NEWS                             |  4 ++
 gdb/doc/gdb.texinfo                  |  5 +++
 gdb/reggroups.c                      | 15 ++------
 gdb/target-descriptions.c            | 73 ++++++++++++++++++------------------
 gdb/testsuite/gdb.base/reggroups.c   |  4 ++
 gdb/testsuite/gdb.base/reggroups.exp | 71 +++++++++++++++++++++++++++++++++++
 gdb/testsuite/gdb.xml/extra-regs.xml |  1 +
 gdb/testsuite/gdb.xml/tdesc-regs.exp |  3 ++
 8 files changed, 128 insertions(+), 48 deletions(-)
 create mode 100644 gdb/testsuite/gdb.base/reggroups.c
 create mode 100644 gdb/testsuite/gdb.base/reggroups.exp

-- 
2.9.4

             reply	other threads:[~2017-06-07 22:15 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-07 22:15 Stafford Horne [this message]
2017-06-07 22:16 ` [PATCH 2/3] reggroups: Convert reggroups from post_init to pre_init Stafford Horne
2017-06-07 22:16 ` [PATCH 3/3] tdesc: handle arbitrary strings in tdesc_register_in_reggroup_p Stafford Horne
2017-06-08  2:40   ` Eli Zaretskii
2017-06-08  5:01     ` Stafford Horne
2017-06-08 14:56       ` Eli Zaretskii
2017-06-08 20:52   ` Simon Marchi
2017-06-09 11:45     ` Stafford Horne
2017-06-09 19:59       ` Simon Marchi
2017-06-10  8:17         ` Stafford Horne
2017-06-13 11:17   ` Pedro Alves
2017-06-07 22:16 ` [PATCH 1/3] reggroups: Add test and docs for `info reg $reggroup` feature Stafford Horne
2017-06-08  2:38   ` Eli Zaretskii
2017-06-08  4:59     ` Stafford Horne
2017-06-08 20:31   ` Simon Marchi
2017-06-08 23:27     ` Stafford Horne
2017-06-09  6:20       ` Simon Marchi
2017-06-13 11:17   ` Pedro Alves

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=cover.1496871270.git.shorne@gmail.com \
    --to=shorne@gmail.com \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).