public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Guinevere Larsen <blarsen@redhat.com>
To: Guinevere Larsen <blarsen@redhat.com>,
	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH v2 0/3] Small step in supporting AVX instructions
Date: Mon, 24 Jun 2024 14:49:16 -0300	[thread overview]
Message-ID: <d6b7985f-afbe-4dd6-8d1e-8543d742b301@redhat.com> (raw)
In-Reply-To: <20240611154500.259754-1-blarsen@redhat.com>

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

On 6/11/24 12:44 PM, Guinevere Larsen wrote:
> This patch series is the first, very small, step in supporting AVX and
> AVX2 instructions for the record-full target. It is important that we
> support it since glibc has been using avx instructions for a long time
> (at least fedora 21), so depending on which functions an inferior uses,
> they might be very inconvenienced.
>
> Patch 1 adds capability to identify the VEX prefix, but no instruction
> support. Patches 2 and 3 add support for a total of 10 instructions,
> which covers around 5% of all AVX instructions used by system libraries
> in my fedora 39 box.
>
> While this support is extremely minimal, I figured I could propose the
> patch series early so it was open for others with more free time could
> help contributing to this :)
>
> ---
> Changes for v2:
> * stopped using "error" when finding incorrect encoding in vmov
>    instructions, as suggested by Tom Tromey.
> * Changed i386-avx-reverse test, to stop failing with clang.
> * Changed the KFAIL in gdb.reverse/step-precsave, so we don't get new
>    FAILs while AVX support is incomplete.
>
> Guinevere Larsen (3):
>    gdb: Start supporting AVX instruction
>    gdb/record: add support to vmovd and vmovq instructions
>    gdb/record: add support to AVX unpack instructions
>
>   gdb/amd64-tdep.c                              |   3 +-
>   gdb/i386-tdep.c                               | 173 ++++++++++++++-
>   gdb/i386-tdep.h                               |   2 +
>   gdb/testsuite/gdb.reverse/i386-avx-reverse.c  | 138 ++++++++++++
>   .../gdb.reverse/i386-avx-reverse.exp          | 203 ++++++++++++++++++
>   gdb/testsuite/gdb.reverse/step-precsave.exp   |   4 +-
>   6 files changed, 518 insertions(+), 5 deletions(-)
>   create mode 100644 gdb/testsuite/gdb.reverse/i386-avx-reverse.c
>   create mode 100644 gdb/testsuite/gdb.reverse/i386-avx-reverse.exp
>


  parent reply	other threads:[~2024-06-24 17:49 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 ` Guinevere Larsen [this message]
2024-06-25  7:28   ` [PATCH v2 0/3] Small step in supporting AVX instructions Willgerodt, Felix
2024-06-25 11:46     ` Guinevere Larsen

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=d6b7985f-afbe-4dd6-8d1e-8543d742b301@redhat.com \
    --to=blarsen@redhat.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).