From: Guinevere Larsen <blarsen@redhat.com>
To: Guinevere Larsen <blarsen@redhat.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: [PING][PATCH 0/3] Small step in supporting AVX instructions
Date: Tue, 4 Jun 2024 16:10:14 -0300 [thread overview]
Message-ID: <a204307c-ced4-444e-b75b-d43afe6ea056@redhat.com> (raw)
In-Reply-To: <20240521202800.2865871-1-blarsen@redhat.com>
Ping!
Since this patch is only x86 record full, if there are no comments until
next week, I will push this change.
--
Cheers,
Guinevere Larsen
She/Her/Hers
On 5/21/24 17:27, 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 :)
>
> As for filed bugs, there are 2 that I could find on bugzilla, but both
> name a specific instruction (vmovdqa and vmovdqu) which were not added
> by this series, so I figured I should only mention it once those are
> added.
>
> 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 | 170 ++++++++++++++-
> gdb/i386-tdep.h | 2 +
> gdb/testsuite/gdb.reverse/i386-avx-reverse.c | 127 +++++++++++
> .../gdb.reverse/i386-avx-reverse.exp | 197 ++++++++++++++++++
> 5 files changed, 496 insertions(+), 3 deletions(-)
> create mode 100644 gdb/testsuite/gdb.reverse/i386-avx-reverse.c
> create mode 100644 gdb/testsuite/gdb.reverse/i386-avx-reverse.exp
>
next prev parent reply other threads:[~2024-06-04 19:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-21 20:27 [PATCH " Guinevere Larsen
2024-05-21 20:27 ` [PATCH 1/3] gdb: Start supporting AVX instruction Guinevere Larsen
2024-06-05 16:11 ` Tom Tromey
2024-06-05 17:33 ` Guinevere Larsen
2024-06-06 17:01 ` Tom Tromey
2024-05-21 20:27 ` [PATCH 2/3] gdb/record: add support to vmovd and vmovq instructions Guinevere Larsen
2024-06-05 16:13 ` Tom Tromey
2024-06-05 18:24 ` Guinevere Larsen
2024-06-05 19:53 ` Guinevere Larsen
2024-05-21 20:28 ` [PATCH 3/3] gdb/record: add support to AVX unpack instructions Guinevere Larsen
2024-06-04 19:10 ` Guinevere Larsen [this message]
2024-06-05 16:13 ` [PING][PATCH 0/3] Small step in supporting AVX instructions Tom Tromey
2024-06-06 8:16 ` Willgerodt, Felix
2024-06-06 12:50 ` Guinevere Larsen
2024-06-06 13:36 ` Willgerodt, Felix
2024-06-06 13:45 ` 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=a204307c-ced4-444e-b75b-d43afe6ea056@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).