Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Sam James <sam@gentoo.org>
To: Simon Marchi <simark@simark.ca>
Cc: Tom de Vries <tdevries@suse.de>,
	 "Gerlicher, Klaus" <klaus.gerlicher@intel.com>,
	 "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] [gdb/tdep] Add XOP support in amd64_get_insn_details
Date: Wed, 27 Aug 2025 15:47:04 +0100	[thread overview]
Message-ID: <87y0r4om8n.fsf@gentoo.org> (raw)
In-Reply-To: <56ce255a-78cb-4759-9dc4-4fec9334c9a4@simark.ca>

Simon Marchi <simark@simark.ca> writes:

> On 8/26/25 3:42 PM, Tom de Vries wrote:
>> On 8/26/25 15:20, Gerlicher, Klaus wrote:
>>> Hi Tom,
>>>
>>> Thanks for working on this, I was tempted to also add it also but since this is only supported on 10 year old AMD CPUs, so I didn't bother.
>>>
>> 
>> Hi Klaus,
>> 
>> thanks for the review.
>> 
>> FWIW, I don't know how relevant this patch is, but new gdbs are used on both older and recent architectures, so it could be relevant for someone.
>
> OOC, do compilers actually produce these instructions by default?  I
> would guess not.  Do they produce them if you select the right
> -mcpu/-march?  Perhaps they appear in some ifunc specifically crafted
> for these CPUs?

Yeah, they appear with the right -march=. It came up recently with the
kernel even: https://lore.kernel.org/regressions/175386161199.564247.597496379413236944.stgit@devnote2/

sam

      reply	other threads:[~2025-08-27 14:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-26  8:59 Tom de Vries
2025-08-26 13:20 ` Gerlicher, Klaus
2025-08-26 19:42   ` Tom de Vries
2025-08-27 14:36     ` Simon Marchi
2025-08-27 14:47       ` Sam James [this message]

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=87y0r4om8n.fsf@gentoo.org \
    --to=sam@gentoo.org \
    --cc=gdb-patches@sourceware.org \
    --cc=klaus.gerlicher@intel.com \
    --cc=simark@simark.ca \
    --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