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]

Re: [PATCH] Print vector registers in natural format, not hex


Eli Zaretskii <eliz@is.elta.co.il> writes:

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.

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.
The wording was lifted from ``info float''. The assumption is that the architecture backend will eventually find it necessary customize these commands. For the architectures I've looked at (Intel's SSE and WMMX) an ``info vector'' command ends up needing to print both true vector registers and some associated status registers. The (er now legendary) reggroups code addresses much of this problem.

I don't think we need ``info fp-registers'' or ``info vector-registers'' commands.

Andrew



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]