From: John Baldwin <jhb@FreeBSD.org>
To: Tom Tromey <tromey@adacore.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 0/3] Minor cleanups in disassemble code
Date: Fri, 22 Mar 2024 10:59:05 -0700 [thread overview]
Message-ID: <b091afad-5232-4151-954e-2db67648d159@FreeBSD.org> (raw)
In-Reply-To: <20240321-disassemble-cleanup-v1-0-77448506f4ab@adacore.com>
On 3/21/24 11:10 AM, Tom Tromey wrote:
> I happened to look at the disassemble code today, and I saw a few
> minor changes that, IMO, make it a bit cleaner.
>
> Regression tested on x86-64 Fedora 38.
>
> ---
> Tom Tromey (3):
> Constify get_disassembler_options
> Remove some unnecessary casts
> Use std::string for disassembler options
>
> gdb/arc-tdep.c | 15 +++++++--------
> gdb/arch-utils.c | 6 +++---
> gdb/arm-tdep.c | 6 +++---
> gdb/disasm.c | 22 +++++++++-------------
> gdb/disasm.h | 2 +-
> gdb/gdbarch-gen.h | 4 ++--
> gdb/gdbarch.c | 6 +++---
> gdb/gdbarch_components.py | 2 +-
> gdb/mips-tdep.c | 14 +++++++-------
> gdb/riscv-tdep.c | 2 +-
> gdb/rs6000-tdep.c | 2 +-
> gdb/s390-tdep.c | 2 +-
> 12 files changed, 39 insertions(+), 44 deletions(-)
> ---
> base-commit: acaf48b921453c37fc2df4151699c912940bcd25
> change-id: 20240321-disassemble-cleanup-5da01a245e74
>
> Best regards,
These all seem sensible. It seems a bit odd to me that
gdbarch_disassembler_options returns a pointer to the string rather
than the string, but that was true before and not related to your
changes.
Approved-By: John Baldwin <jhb@FreeBSD.org>
--
John Baldwin
next prev parent reply other threads:[~2024-03-22 17:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-21 18:10 Tom Tromey
2024-03-21 18:10 ` [PATCH 1/3] Constify get_disassembler_options Tom Tromey
2024-03-21 18:10 ` [PATCH 2/3] Remove some unnecessary casts Tom Tromey
2024-03-21 18:10 ` [PATCH 3/3] Use std::string for disassembler options Tom Tromey
2024-03-22 17:59 ` John Baldwin [this message]
2024-03-22 19:12 ` [PATCH 0/3] Minor cleanups in disassemble code 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=b091afad-5232-4151-954e-2db67648d159@FreeBSD.org \
--to=jhb@freebsd.org \
--cc=gdb-patches@sourceware.org \
--cc=tromey@adacore.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