From: Helge Deller <deller@gmx.de>
To: "Alex Bennée" <alex.bennee@linaro.org>, qemu-devel@nongnu.org
Cc: Richard Henderson <richard.henderson@linaro.org>
Subject: Re: [RFC PATCH] disas/hppa: drop raw opcode dump
Date: Thu, 29 Feb 2024 16:02:09 +0100 [thread overview]
Message-ID: <83e2986e-3c80-4cf3-93ae-5e578051c98b@gmx.de> (raw)
In-Reply-To: <20240229140557.1749767-1-alex.bennee@linaro.org>
On 2/29/24 15:05, Alex Bennée wrote:
> The hppa disassembly is different from the others due to leading with
> the raw opcode data. This confuses plugins looking for instruction
> prefixes to match instructions. For plugins like execlog there is
> another mechanism for getting the instruction byte data.
>
> For the sake of consistently just present the instruction assembly
> code.
>
> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
This effectively reverts commit 2f926bfd5b79e6219ae65a1e530b38f37d62b384
("disas/hppa: Show hexcode of instruction along with disassembly").
Sad, but Ok.
Acked-by: Helge Deller <deller@gmx.de>
> ---
> disas/hppa.c | 4 ----
> 1 file changed, 4 deletions(-)
>
> diff --git a/disas/hppa.c b/disas/hppa.c
> index 22dce9b41bb..dd34cce211b 100644
> --- a/disas/hppa.c
> +++ b/disas/hppa.c
> @@ -1972,10 +1972,6 @@ print_insn_hppa (bfd_vma memaddr, disassemble_info *info)
>
> insn = bfd_getb32 (buffer);
>
> - info->fprintf_func(info->stream, " %02x %02x %02x %02x ",
> - (insn >> 24) & 0xff, (insn >> 16) & 0xff,
> - (insn >> 8) & 0xff, insn & 0xff);
> -
> for (i = 0; i < NUMOPCODES; ++i)
> {
> const struct pa_opcode *opcode = &pa_opcodes[i];
next prev parent reply other threads:[~2024-02-29 15:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 14:05 [RFC PATCH] disas/hppa: drop raw opcode dump Alex Bennée
2024-02-29 15:02 ` Helge Deller [this message]
2024-02-29 16:41 ` Alex Bennée
2024-02-29 18:11 ` Richard Henderson
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=83e2986e-3c80-4cf3-93ae-5e578051c98b@gmx.de \
--to=deller@gmx.de \
--cc=alex.bennee@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.