Re: [eliz@is.elta.co.il: GDB: fine print in 387 info]

[Jim Blandy <jimb@cygnus.com>]

> But this means that "info float" becomes redundant.  I prefer another
> approach, where "info all-registers" displays the registers with the
> names they should be referred to if the user wants e.g. to change
> their values, while "info float" presents an alternative view of the
> FPU status.  Therefore, my suggestion below does not necessarily
> follow the FP registers names.

What exactly is the additional information you want "info float" to
show that "info all-registers" cannot show?

"info float" is an opportunity to provide information that "info
all-registers" cannot, but since the latter is allowed to print out
nice human-readable versions of flags, etc. to the right of the raw
value, it can provide quite a bit of information.  Where possible,
they should use the same format.  The only thing I can think of,
offhand, that "all-registers" can't show gracefully is the
TOS/physical FP register mapping.