From: Andrew Burgess <andrew.burgess@embecosm.com>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tom@tromey.com>,
Andrew Burgess <andrew.burgess@embecosm.com>
Subject: [PATCHv2 0/2] Improvements to Python Register Descriptor API
Date: Tue, 14 Jul 2020 18:14:29 +0100 [thread overview]
Message-ID: <cover.1594746770.git.andrew.burgess@embecosm.com> (raw)
In-Reply-To: <cover.1594197735.git.andrew.burgess@embecosm.com>
Changes from v1:
- Data structures in both patches now hold gdbpy_ref<> as suggested
by Tom.
Thanks,
Andrew
---
Andrew Burgess (2):
gdb/python: Reuse gdb.RegisterDescriptor objects where possible
gdb/python: Reuse gdb.RegisterGroup objects where possible
gdb/ChangeLog | 19 ++++
gdb/python/py-registers.c | 102 +++++++++++++-----
gdb/testsuite/ChangeLog | 8 ++
.../gdb.python/py-arch-reg-groups.exp | 19 ++++
.../gdb.python/py-arch-reg-names.exp | 19 ++++
5 files changed, 143 insertions(+), 24 deletions(-)
--
2.25.4
next prev parent reply other threads:[~2020-07-14 17:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-08 8:48 [PATCH " Andrew Burgess
2020-07-08 8:48 ` [PATCH 1/2] gdb/python: Reuse gdb.RegisterDescriptor objects where possible Andrew Burgess
2020-07-13 18:21 ` Tom Tromey
2020-07-08 8:48 ` [PATCH 2/2] gdb/python: Reuse gdb.RegisterGroup " Andrew Burgess
2020-07-13 18:23 ` Tom Tromey
2020-07-14 17:14 ` Andrew Burgess [this message]
2020-07-14 17:14 ` [PATCHv2 1/2] gdb/python: Reuse gdb.RegisterDescriptor " Andrew Burgess
2020-07-22 13:10 ` Pedro Alves
2020-07-22 14:05 ` Andrew Burgess
2020-07-22 14:32 ` Pedro Alves
2020-07-22 15:10 ` Andrew Burgess
2020-07-14 17:14 ` [PATCHv2 2/2] gdb/python: Reuse gdb.RegisterGroup " Andrew Burgess
2020-07-21 18:26 ` [PATCHv2 0/2] Improvements to Python Register Descriptor API Tom Tromey
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.1594746770.git.andrew.burgess@embecosm.com \
--to=andrew.burgess@embecosm.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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