public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "guinevere at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug record/19365] gdb record fail to recognize vmovdqa avx instruction.
Date: Mon, 28 Oct 2024 14:25:21 +0000 [thread overview]
Message-ID: <bug-19365-4717-mhzboyT0Sg@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-19365-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=19365
Guinevere Larsen <guinevere at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|NEW |RESOLVED
CC| |guinevere at redhat dot com
--- Comment #3 from Guinevere Larsen <guinevere at redhat dot com> ---
This issue has been fixed by a commit I pushed today (and unfortunately forgot
to add the Bug: trailer):
commit 5bf288d5a88ab6d3fa9bd7bd070e624afd264dc6
Author: Guinevere Larsen <guinevere@redhat.com>
Date: Fri Jul 26 17:31:14 2024 -0300
gdb/record: support AVX instructions VMOVDQ(U|A) when recording
This commit adds support for the instructions VMOVDQU and VMOVDQA, used
to move values to/from 256 bit registers. Unfortunately, the
programmer's manual is very incomplete (if not wrong) about these
instructions, so the logic had to be reverse engineered from how gcc
actually encodes the instruction.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2024-10-28 14:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-19365-4717@http.sourceware.org/bugzilla/>
2022-07-05 17:45 ` code@reto-schneider.ch
2024-10-28 14:25 ` guinevere at redhat dot com [this message]
2024-10-28 14:37 ` sam at gentoo dot org
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=bug-19365-4717-mhzboyT0Sg@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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).