From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24931 invoked by alias); 22 Oct 2002 00:23:57 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 24918 invoked from network); 22 Oct 2002 00:23:55 -0000 Received: from unknown (HELO touchme.toronto.redhat.com) (216.138.202.10) by sources.redhat.com with SMTP; 22 Oct 2002 00:23:55 -0000 Received: from localhost.redhat.com (to-dhcp51.toronto.redhat.com [172.16.14.151]) by touchme.toronto.redhat.com (Postfix) with ESMTP id 09579800084 for ; Mon, 21 Oct 2002 20:23:55 -0400 (EDT) Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 2C9CF3E13; Mon, 21 Oct 2002 20:23:54 -0400 (EDT) Message-ID: <3DB49A9A.9080706@redhat.com> Date: Mon, 21 Oct 2002 17:23:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.0) Gecko/20020824 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Klee Dienes Cc: Eli Zaretskii , gdb-patches@sources.redhat.com Subject: Re: [PATCH] Print vector registers in natural format, not hex References: <22199F8A-DD36-11D6-B6D6-00039396EEB8@apple.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-10/txt/msg00373.txt.bz2 > Eli Zaretskii 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