Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Hannes Domani <ssbssa@yahoo.de>
To: Tom Tromey <tom@tromey.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH v3 6/8] Windows gdb: Get available XState features
Date: Tue, 1 Sep 2026 17:44:22 +0000 (UTC)	[thread overview]
Message-ID: <542062786.23931.1788284662884@mail.yahoo.com> (raw)
In-Reply-To: <875x0o7tza.fsf@tromey.com>

 Am Dienstag, 1. September 2026 um 19:38:06 MESZ hat Tom Tromey <tom@tromey.com> Folgendes geschrieben:

> >>>>> "Hannes" == Hannes Domani <ssbssa@yahoo.de> writes:
> 
> Hannes> Also prepares the thread context for the additional registers.
> Hannes> ---
> Hannes> v2:
> Hannes>  - Remove PKRU from the implemented features mask
> Hannes> v3:
> Hannes>  - use throw_winerror_with_name instead of error
> Hannes>  - fix formatting and value of xstate_features
> 
> Thanks.
> 
> Hannes> +      /* Available XState features masked with implemented features.  */
> Hannes> +      xstate_features = (GetEnabledXStateFeatures ()
> Hannes> +            & X86_XSTATE_SSE_MASK);
> Hannes> +      /* The extended XState functions are only needed if the available
> Hannes> +    features exceed SSE.  */
> Hannes> +      if ((xstate_features & ~X86_XSTATE_SSE_MASK) == 0)
> Hannes> +    xstate_features = 0;
> 
> Won't this condition always be true?
> Resulting in xstate_features==0 always?

Yes, with this patch xstate_features is still 0.
The next patch then changes the 'and' of the first xstate_features to use
X86_XSTATE_AVX_MASK instead, so it will be possible to have other values.


Hannes

  reply	other threads:[~2026-09-01 17:44 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260829145823.1034821-1-ssbssa.ref@yahoo.de>
2026-08-29 14:48 ` [PATCH v3 1/8] gdb/testsuite: Add Windows replacement for aligned_alloc Hannes Domani
2026-08-29 14:48   ` [PATCH v3 2/8] Windows gdb: Use allocated buffer for CONTEXT Hannes Domani
2026-09-01 17:22     ` Tom Tromey
2026-09-01 17:30       ` Hannes Domani
2026-08-29 14:49   ` [PATCH v3 3/8] Windows gdb: Remove mappings member from windows_per_inferior Hannes Domani
2026-08-29 14:49   ` [PATCH v3 4/8] Windows gdb: Refactor getting pointer to register inside context Hannes Domani
2026-08-29 14:49   ` [PATCH v3 5/8] Windows gdb: Prepare XState functions Hannes Domani
2026-08-29 14:49   ` [PATCH v3 6/8] Windows gdb: Get available XState features Hannes Domani
2026-09-01 17:38     ` Tom Tromey
2026-09-01 17:44       ` Hannes Domani [this message]
2026-09-01 17:51         ` Tom Tromey
2026-08-29 14:49   ` [PATCH v3 7/8] Windows gdb: Implement AVX register support Hannes Domani
2026-09-01 17:48     ` Tom Tromey
2026-09-01 18:00       ` Hannes Domani
2026-09-08 15:27         ` Joos, Christina
2026-09-04 16:33       ` Joos, Christina
2026-09-08 13:04     ` Rohr, Stephan
2026-09-10 11:33       ` Joos, Christina
2026-08-29 14:49   ` [PATCH v3 8/8] Windows gdb: Implement AVX-512 " Hannes Domani
2026-08-29 15:40     ` Eli Zaretskii
2026-09-01 17:49     ` Tom Tromey
2026-09-08 13:05     ` Rohr, Stephan
2026-09-10 12:08       ` Joos, Christina
2026-09-10 14:39         ` Hannes Domani
2026-09-13 21:18           ` Joos, Christina
2026-09-10 16:54         ` Hannes Domani
2026-09-13 21:37           ` Joos, 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=542062786.23931.1788284662884@mail.yahoo.com \
    --to=ssbssa@yahoo.de \
    --cc=gdb-patches@sourceware.org \
    --cc=tom@tromey.com \
    /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