x86 FPU support: "info float" and `long double'
Eli Zaretskii
eliz@gnu.org
Thu Oct 21 10:41:00 GMT 1999
> My current gdb has
>
> (gdb) info float
> st0: 0x3ffed6d6d6d6d6d6d800 Empty Normal 0.8392156862745098200307
> st1: 0x00000000000000000000 Empty Zero 0
"st0", "st1" etc. implies stack-relative order of the registers.
IMHO, this is wrong: it doesn't present the registers as a stack, and
with each push/pop operation, the entire picture moves up/down, which
is very confusing. If this format is adopted (I hope not), it won't
make sense to print the TOS pointer (that arrow => shown by Mark in
his example), since the TOS is always st0.
In the physical order, like what go32-nat.c does, the registers cannot
be designated st0, st1, etc., because that's not true. If 0, 1,
etc. is somehow not good enough, we should use R0, R1, etc., like
Intel does.
More information about the Gdb
mailing list