diff options
| author | Guinevere Larsen <guinevere@redhat.com> | 2024-07-29 14:52:59 -0300 |
|---|---|---|
| committer | Guinevere Larsen <guinevere@redhat.com> | 2024-10-28 10:46:33 -0300 |
| commit | 4b672a4a6d087a12ff24cb5125dbbb5dfa876b9a (patch) | |
| tree | b8294305e763e68bf480fc6e84dcebb77b5e40ca /gdb/python/py-finishbreakpoint.c | |
| parent | 13f011367694444778dde4600dd86ae79ad8beec (diff) | |
| download | gdb-4b672a4a6d087a12ff24cb5125dbbb5dfa876b9a.zip gdb-4b672a4a6d087a12ff24cb5125dbbb5dfa876b9a.tar.gz gdb-4b672a4a6d087a12ff24cb5125dbbb5dfa876b9a.tar.bz2 | |
gdb/record: add support to vmovd and vmovq instructions
This commit adds support to the x86_64 AVX instructions vmovd and vmovq.
The programmers manuals for Intel and AMD describe these 2 instructions
as being almost the same, but my local testing, using gcc 13.2 on Fedora
39, showed several differences and inconsistencies.
The instruction is supposed to always use the 3-byte VEX prefix, but I
could only find 2-byte versions. The instructions aren't differentiated
by the VEX.w bit, but by opcodes and VEX.pp.
This patch adds a test with many different uses for both vmovd and
vmovq. It also updates the test gdb.reverse/step-precsave.exp to
reference the generic "missing avx support" bug open in the bug tracker
(17346), instead of pointing to one that specifically calls out to
vmovd instructions.
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=23188
Approved-By: Tom Tromey <tom@tromey.com>
Diffstat (limited to 'gdb/python/py-finishbreakpoint.c')
0 files changed, 0 insertions, 0 deletions