This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Eli Zaretskii <eliz@is.elta.co.il> writes:
The closest facility is the 'info vector' command, which by default prints the contents of all vector registers, but is documented simply as "Print the status of the vector unit.", which I take to mean that it can be overridden to have arch-specific output, much like 'info float'. An 'info vector-registers' and 'info fp-registers' command might not be such a bad idea, but none exists at the moment that I know of.Thanks, this is approved. Do we have facilities for printing vector registers? If so, we should probably add a cross-reference to their description here. The intersted reader will most probably wonder what can she do to print vector registers when she reads these passages.
@value{GDBN} always considers the contents of an ordinary register as anMaybe something along the lines of:
integer when the register is examined in this way. Some machines have
special registers which can hold nothing but floating point; these
registers are considered to have floating point values. There is no way
to refer to the contents of an ordinary register as floating point value
(although you can @emph{print} it as a floating point value with
@samp{print/f $@var{regname}}).
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |