From: Stafford Horne <shorne@gmail.com>
To: GDB patches <gdb-patches@sourceware.org>
Cc: Stafford Horne <shorne@gmail.com>
Subject: [PATCH v2 0/4] Support for arbitrary reggroups
Date: Sat, 10 Jun 2017 13:59:00 -0000 [thread overview]
Message-ID: <cover.1497102900.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.
This series also adds documentation on tests for the feature of listing
register groups via the "info reg $reggroup" command.
-Stafford
--
Changes since v1
* On 'info reg $reggroup' test and docs patch
- Suggested by Eli - Fix changelog
- Suggested by Simon
> Added help text in 'help info registers'
> Fixed 'register' typos
> Fixed style of test program
> Fixed copyright '2017'
> Fixed code styles in expect
* On 'arbitrary strings' patch
- Suggested by Simon
> Allow for freeing reggroups
- Suggested by Eli
> Add documentation for this feature
Stafford Horne (4):
reggroups: Add test and docs for `info reg $reggroup` feature
reggroups: Convert reggroups from post_init to pre_init
reggroups: Create reggroup_gdbarch_new for dynamic reggroups
tdesc: handle arbitrary strings in tdesc_register_in_reggroup_p
gdb/NEWS | 4 ++
gdb/doc/gdb.texinfo | 14 +++++--
gdb/infcmd.c | 8 +++-
gdb/reggroups.c | 27 +++++++------
gdb/reggroups.h | 4 ++
gdb/target-descriptions.c | 74 ++++++++++++++++++------------------
gdb/testsuite/gdb.base/reggroups.c | 5 +++
gdb/testsuite/gdb.base/reggroups.exp | 63 ++++++++++++++++++++++++++++++
gdb/testsuite/gdb.xml/extra-regs.xml | 1 +
gdb/testsuite/gdb.xml/tdesc-regs.exp | 3 ++
10 files changed, 149 insertions(+), 54 deletions(-)
create mode 100644 gdb/testsuite/gdb.base/reggroups.c
create mode 100644 gdb/testsuite/gdb.base/reggroups.exp
--
2.9.4
next reply other threads:[~2017-06-10 13:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-10 13:59 Stafford Horne [this message]
2017-06-10 13:59 ` [PATCH v2 4/4] tdesc: handle arbitrary strings in tdesc_register_in_reggroup_p Stafford Horne
2017-06-10 13:59 ` [PATCH v2 2/4] reggroups: Convert reggroups from post_init to pre_init Stafford Horne
2017-06-10 13:59 ` [PATCH v2 1/4] reggroups: Add test and docs for `info reg $reggroup` feature Stafford Horne
2017-06-10 13:59 ` [PATCH v2 3/4] reggroups: Create reggroup_gdbarch_new for dynamic reggroups Stafford Horne
2017-06-10 14:03 ` [PATCH v2 0/4] Support for arbitrary reggroups Eli Zaretskii
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.1497102900.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