From: Andrew Burgess <aburgess@redhat.com>
To: gdb-patches@sourceware.org
Cc: Andrew Burgess <aburgess@redhat.com>
Subject: [PATCH 0/2] Some changes to the gdbarch*.py scripts
Date: Thu, 10 Mar 2022 13:31:22 +0000 [thread overview]
Message-ID: <cover.1646918997.git.aburgess@redhat.com> (raw)
A couple of changes to the gdb/gdbarch*.py script:
#1: Remove an unused predicate function, and
#2: Extend the verify_gdbarch function to cover more cases.
Thanks,
Andrew
---
Andrew Burgess (2):
gdb/gdbarch: remove the predicate function for gdbarch_register_type
gdb/gdbarch: compare some fields against 0 verify_gdbarch
gdb/gdbarch-components.py | 13 ++++++-------
gdb/gdbarch-gen.h | 2 --
gdb/gdbarch.c | 22 +++++++++++-----------
gdb/gdbarch.py | 10 ++++++++++
4 files changed, 27 insertions(+), 20 deletions(-)
--
2.25.4
next reply other threads:[~2022-03-10 13:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-10 13:31 Andrew Burgess [this message]
2022-03-10 13:31 ` [PATCH 1/2] gdb/gdbarch: remove the predicate function for gdbarch_register_type Andrew Burgess
2022-03-10 17:06 ` Tom Tromey
2022-03-10 13:31 ` [PATCH 2/2] gdb/gdbarch: compare some fields against 0 verify_gdbarch Andrew Burgess
2022-03-10 17:09 ` Tom Tromey
2022-03-14 14:10 ` Andrew Burgess
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.1646918997.git.aburgess@redhat.com \
--to=aburgess@redhat.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).