Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Schimpe, Christina" <christina.schimpe@intel.com>
To: Tom de Vries <tdevries@suse.de>,
	"Gerlicher, Klaus" <klaus.gerlicher@intel.com>,
	Sam James <sam@gentoo.org>, "Beulich, Jan" <JBeulich@suse.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>
Subject: RE: Inconsistent usage on onebyte_modrm and twobyte_modrm table in x86 disassembler and gdb?
Date: Wed, 27 Aug 2025 10:32:52 +0000	[thread overview]
Message-ID: <SN7PR11MB763889CE525179DCDB7AF723F938A@SN7PR11MB7638.namprd11.prod.outlook.com> (raw)
In-Reply-To: <23021f8f-e769-4160-8689-24b9d38b61b6@suse.de>

Hi all, 

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 ?

Kind Regards,
Christina

> -----Original Message-----
> From: Tom de Vries <tdevries@suse.de>
> Sent: Tuesday, August 26, 2025 11:32 AM
> To: Gerlicher, Klaus <klaus.gerlicher@intel.com>; Sam James <sam@gentoo.org>;
> Beulich, Jan <JBeulich@suse.com>
> Cc: Jiang, Haochen <haochen.jiang@intel.com>; Binutils
> <binutils@sourceware.org>; gdb-patches@sourceware.org; H.J.Lu
> <hjl.tools@gmail.com>; Alexander Monakov <amonakov@ispras.ru>
> Subject: Re: Inconsistent usage on onebyte_modrm and twobyte_modrm table
> in x86 disassembler and gdb?
> 
> On 8/26/25 10:19, Gerlicher, Klaus wrote:
> > FWIW I'll attach my fix for the (V)PBLENDW. It has a testcase and a unittest
> case.
> 
> Hi Klaus,
> 
> thanks for working on this.
> 
> The patch LGTM, other than this:
> ...
> $ git show --pretty=%s --check
> Fix vpblendw
> 
> gdb/amd64-tdep.c:1409: space before tab in indent.
> +      	  need_modrm = 1;
> ...
> 
> I've tested both the unit test, and the updated test-case.
> 
> I've also tested the unit test I wrote, which uses vex3 instead of evex:
> ...
> +
> +  /* INSN: vpblendw $0x7,%xmm4,%xmm6,%xmm2, vex3 prefix.  */  insn = {
> + 0xc4, 0xe3, 0x49, 0x0e, 0xd4, 0x07 };  amd64_get_insn_details
> + (insn.data (), &details);  SELF_CHECK (details.opcode_len == 3);
> + SELF_CHECK (details.enc_prefix_offset == 0);  SELF_CHECK
> + (details.opcode_offset == 3);  SELF_CHECK (details.modrm_offset == 4);
> +
> +  /* INSN: vpblendw $0x7,0xff(%rip),%ymm6,%ymm2, vex3 prefix.  */  insn
> + = { 0xc4, 0xe3, 0x4d, 0x0e, 0x15, 0xff, 0x00, 0x00, 0x00, 0x07 };
> + amd64_get_insn_details (insn.data (), &details);  SELF_CHECK
> + (details.opcode_len == 3);  SELF_CHECK (details.enc_prefix_offset ==
> + 0);  SELF_CHECK (details.opcode_offset == 3);  SELF_CHECK
> + (details.modrm_offset == 4);
> +
> +  /* INSN: vpblendw $0x7,0xff(%ecx),%ymm6,%ymm2, vex3 prefix.  */
> + fixup_riprel (details, insn.data (), ECX_REG_NUM);  updated_insn
> +    = { 0xc4, 0xe3, 0x4d, 0x0e, 0x91, 0xff, 0x00, 0x00, 0x00, 0x07 };
> + SELF_CHECK (insn == updated_insn);
> ...
> 
> You could add this as well, but it's not required.
> 
> [ Note that you could drop the test-case update and use fixup_riprel on the unit
> test you added instead, like I did here and is done elsewhere in the unit test. ]
> 
> Please commit this with some appropriate $subject.
> 
> Approved-By: Tom de Vries <tdevries@suse.de>
> 
> Thanks,
> - Tom
Intel Deutschland GmbH
Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Sean Fennelly, Jeffrey Schneiderman, Tiffany Doon Silva
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928

  reply	other threads:[~2025-08-27 10:34 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 [this message]
2025-08-27 12:20           ` Jan Beulich
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=SN7PR11MB763889CE525179DCDB7AF723F938A@SN7PR11MB7638.namprd11.prod.outlook.com \
    --to=christina.schimpe@intel.com \
    --cc=JBeulich@suse.com \
    --cc=amonakov@ispras.ru \
    --cc=binutils@sourceware.org \
    --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