public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Guinevere Larsen <blarsen@redhat.com>
To: "Willgerodt, Felix" <felix.willgerodt@intel.com>,
	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH v2 0/3] Small step in supporting AVX instructions
Date: Tue, 25 Jun 2024 08:46:15 -0300	[thread overview]
Message-ID: <7b0f4341-6898-4a5e-ac60-0d9d6cbf1546@redhat.com> (raw)
In-Reply-To: <MN2PR11MB456666187973A265C91025B78ED52@MN2PR11MB4566.namprd11.prod.outlook.com>

On 6/25/24 4:28 AM, Willgerodt, Felix wrote:
>> -----Original Message-----
>> From: Guinevere Larsen <blarsen@redhat.com>
>> Sent: Montag, 24. Juni 2024 19:49
>> To: Guinevere Larsen <blarsen@redhat.com>; gdb-patches@sourceware.org
>> Subject: Re: [PATCH v2 0/3] Small step in supporting AVX instructions
>>
>> I've made the mistake of wondering about YMM, and noticed that this
>> series fails to save the higher bits of the register.
>>
>> Seeing as it isn't possible to save ymm registers directly yet (more
>> info here[1][2]), and I'd like to avoid having to save ymmh and xmm in
>> this series, I'll wait until the relevant series get approved before
>> sending a v3 of this series
>>
>> --
>> Cheers,
>> Guinevere Larsen
>> She/Her/Hers
>>
> Hi Guinevere,
>
> Did you forget to include links for [1] and [2]? I can't find what you are
> Referencing in your email. And also can't remember reading anything
> related on the mailing list.

oops, yes i did.

[1] 
https://inbox.sourceware.org/gdb-patches/20240621180730.859487-1-blarsen@redhat.com/
[2] 
https://inbox.sourceware.org/gdb-patches/20240621180918.860097-2-blarsen@redhat.com/

>
> And yes the SSE/AVX registers have seen a bit of historical growth, and are
> split up over different XSTATE regions. Though I don't see a way around this
> split in GDB.

Those 5 patches combined should make it possible to read 
pseudo-registers from the regcache we save for the record target.

I say should because I'm still getting some oddities when rebasing my 
series on top of them and testing the changes, though, so I might be 
missing something. I also don't really know anything about XSTATE, so if 
that's also a problem, do let me know!

We could also just save xmm and ymmh registers, but I think using ymm is 
more readable, so I'd prefer to use that if possible.

-- 
Cheers,
Guinevere Larsen
She/Her/Hers

>
> Felix
> 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:[~2024-06-25 11:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-11 15:44 Guinevere Larsen
2024-06-11 15:44 ` [PATCH v2 1/3] gdb: Start supporting AVX instruction Guinevere Larsen
2024-06-11 15:44 ` [PATCH v2 2/3] gdb/record: add support to vmovd and vmovq instructions Guinevere Larsen
2024-06-11 15:45 ` [PATCH v2 3/3] gdb/record: add support to AVX unpack instructions Guinevere Larsen
2024-06-24 17:49 ` [PATCH v2 0/3] Small step in supporting AVX instructions Guinevere Larsen
2024-06-25  7:28   ` Willgerodt, Felix
2024-06-25 11:46     ` Guinevere Larsen [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=7b0f4341-6898-4a5e-ac60-0d9d6cbf1546@redhat.com \
    --to=blarsen@redhat.com \
    --cc=felix.willgerodt@intel.com \
    --cc=gdb-patches@sourceware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).