From: Jan Beulich <jbeulich@suse.com>
To: "Schimpe, Christina" <christina.schimpe@intel.com>
Cc: "Jiang, Haochen" <haochen.jiang@intel.com>,
Binutils <binutils@sourceware.org>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
"H.J.Lu" <hjl.tools@gmail.com>,
Alexander Monakov <amonakov@ispras.ru>,
Tom de Vries <tdevries@suse.de>,
"Gerlicher, Klaus" <klaus.gerlicher@intel.com>,
Sam James <sam@gentoo.org>
Subject: Re: Inconsistent usage on onebyte_modrm and twobyte_modrm table in x86 disassembler and gdb?
Date: Wed, 27 Aug 2025 14:20:05 +0200 [thread overview]
Message-ID: <deccc79e-0014-489b-a795-18642b680a7f@suse.com> (raw)
In-Reply-To: <SN7PR11MB763889CE525179DCDB7AF723F938A@SN7PR11MB7638.namprd11.prod.outlook.com>
On 27.08.2025 12:32, Schimpe, Christina wrote:
> Thanks a lot for working on this. I have followed this thread and also discussed this with Klaus a bit.
> I still wonder, would it make sense to align the logic in x86 disassembler and gdb ?
Well, fundamentally a function like amd64_get_insn_details() should live
in the disassembler (library). Just that, from all I know, the disassembler
isn't set up at all to hand out that kind of information. It would take
quite a bit of re-org to allow that to effectively be a byproduct (as it
ought to be, imo).
Jan
next prev parent reply other threads:[~2025-08-27 12:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <SJ5PPF77D28E3C228C975969E2B0BDB2853EC3EA@SJ5PPF77D28E3C2.namprd11.prod.outlook.com>
[not found] ` <92aea037-9c0e-438f-8a0a-fd52dd2df7bc@suse.com>
2025-08-25 8:45 ` Sam James
2025-08-25 9:26 ` Alexander Monakov
2025-08-25 14:33 ` Tom de Vries
2025-08-26 6:02 ` Jiang, Haochen
2025-08-26 8:19 ` Gerlicher, Klaus
2025-08-26 9:31 ` Tom de Vries
2025-08-27 10:32 ` Schimpe, Christina
2025-08-27 12:20 ` Jan Beulich [this message]
2025-08-27 15:23 ` Schimpe, Christina
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=deccc79e-0014-489b-a795-18642b680a7f@suse.com \
--to=jbeulich@suse.com \
--cc=amonakov@ispras.ru \
--cc=binutils@sourceware.org \
--cc=christina.schimpe@intel.com \
--cc=gdb-patches@sourceware.org \
--cc=haochen.jiang@intel.com \
--cc=hjl.tools@gmail.com \
--cc=klaus.gerlicher@intel.com \
--cc=sam@gentoo.org \
--cc=tdevries@suse.de \
/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