From: Hannes Domani <ssbssa@yahoo.de>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
"Schimpe, Christina" <christina.schimpe@intel.com>
Subject: Re: [PATCH 5/8] Windows gdb: Prepare XState functions
Date: Fri, 17 Jul 2026 15:07:25 +0000 (UTC) [thread overview]
Message-ID: <1269227151.3498217.1784300845483@mail.yahoo.com> (raw)
In-Reply-To: <2142345607.3489153.1784300647475@mail.yahoo.com>
Am Freitag, 17. Juli 2026 um 17:04:51 MESZ hat Hannes Domani <ssbssa@yahoo.de> Folgendes geschrieben:
> Am Freitag, 17. Juli 2026 um 16:41:54 MESZ hat Schimpe, Christina <christina.schimpe@intel.com> Folgendes geschrieben:
>
> > > -----Original Message-----
> > > From: Hannes Domani <ssbssa@yahoo.de>
> > > Sent: Sonntag, 12. Juli 2026 13:32
> > > To: gdb-patches@sourceware.org
> > > Subject: [PATCH 5/8] Windows gdb: Prepare XState functions
> > >
> > > These functions will then be used to access the XState registers.
> > > ---
> > > gdb/nat/windows-nat.c | 31 +++++++++++ gdb/nat/windows-nat.h | 116
> > > ++++++++++++++++++++++++++++++++++++++++++
> >
> > For this and the following patch: I can see that you introduced x86 specific code,
> > but used the generic windows-nat.c/.h files for it. In gdb linux code we try to keep
> > arch specific details in separate files.
> >
> > In an earlier patch you tried to keep it separate for windows, too:
> > "Move x86 register code into x86-windows-nat.c ".
> >
> > I am not familiar with windows specific code, but do you think moving this to an arch
> > specific file (for instance gdb/x86-windows-nat.c) is an option?
>
> Yes, I tried keeping them separate, but these functions are also used by
> gdbserver, so they have to be in a nat/ header, which makes this a bit
> more complicated.
>
> But I recently found out that Windows apparently also provides SVE registers
> for ARM64 with these same XState functions [1], so if we plan to support that,
> we would probably just move them back here anyways.
Of course I had to forget to include the link...
[1] https://github.com/llvm/llvm-project/pull/205906
Hannes
next prev parent reply other threads:[~2026-07-17 15:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260712113229.3695246-1-ssbssa.ref@yahoo.de>
2026-07-12 11:32 ` [PATCH 1/8] gdb/testsuite: Add Windows replacement for aligned_alloc Hannes Domani
2026-07-12 11:32 ` [PATCH 2/8] Windows gdb: Use allocated buffer for CONTEXT Hannes Domani
2026-07-12 11:32 ` [PATCH 3/8] Windows gdb: Remove mappings member from windows_per_inferior Hannes Domani
2026-07-12 11:32 ` [PATCH 4/8] Windows gdb: Refactor getting pointer to register inside context Hannes Domani
2026-07-12 11:32 ` [PATCH 5/8] Windows gdb: Prepare XState functions Hannes Domani
2026-07-17 14:41 ` Schimpe, Christina
2026-07-17 15:04 ` Hannes Domani
2026-07-17 15:07 ` Hannes Domani [this message]
2026-07-17 16:22 ` Schimpe, Christina
2026-07-12 11:32 ` [PATCH 6/8] Windows gdb: Get available XState features Hannes Domani
2026-07-12 11:32 ` [PATCH 7/8] Windows gdb: Implement XState (Intel AVX) support Hannes Domani
2026-07-17 12:54 ` Schimpe, Christina
2026-07-17 13:46 ` Hannes Domani
2026-07-17 14:16 ` Schimpe, Christina
2026-07-17 14:49 ` Hannes Domani
2026-07-17 15:26 ` Schimpe, Christina
2026-07-17 16:26 ` Hannes Domani
2026-07-17 19:06 ` Schimpe, Christina
2026-07-18 16:06 ` Hannes Domani
2026-07-12 11:32 ` [PATCH 8/8] Windows gdbserver: " Hannes Domani
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=1269227151.3498217.1784300845483@mail.yahoo.com \
--to=ssbssa@yahoo.de \
--cc=christina.schimpe@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