summaryrefslogtreecommitdiff
path: root/meson.build
diff options
context:
space:
mode:
authorTaiseiIto <taisei1212@outlook.jp>2022-12-19 13:04:12 +0900
committerPaolo Bonzini <pbonzini@redhat.com>2023-02-21 13:46:49 +0100
commit49be78ca02a687ea00ad7534254217b479a4e92d (patch)
tree40b0c6834d419686db84aec1615750bac758db83 /meson.build
parent8d0efbcfa0656bef76e95d40933b6243feca58c9 (diff)
downloadqemu-49be78ca02a687ea00ad7534254217b479a4e92d.tar.gz
target/i386/gdbstub: Fix a bug about order of FPU stack in 'g' packets.
Before this commit, when GDB attached an OS working on QEMU, order of FPU stack registers printed by GDB command 'info float' was wrong. There was a bug causing the problem in 'g' packets sent by QEMU to GDB. The packets have values of registers of machine emulated by QEMU containing FPU stack registers. There are 2 ways to specify a x87 FPU stack register. The first is specifying by absolute indexed register names (R0, ..., R7). The second is specifying by stack top relative indexed register names (ST0, ..., ST7). Values of the FPU stack registers should be located in 'g' packet and be ordered by the relative index. But QEMU had located these registers ordered by the absolute index. After this commit, when QEMU reads registers to make a 'g' packet, QEMU specifies FPU stack registers by the relative index. Then, the registers are ordered correctly in the packet. As a result, GDB, the packet receiver, can print FPU stack registers in the correct order. Signed-off-by: TaiseiIto <taisei1212@outlook.jp> Reviewed-by: Richard Henderson <richard.henderson@linaro.org> Message-Id: <TY0PR0101MB4285923FBE9AD97CE832D95BA4E59@TY0PR0101MB4285.apcprd01.prod.exchangelabs.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'meson.build')
0 files changed, 0 insertions, 0 deletions