From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21850 invoked by alias); 9 Aug 2002 02:35:14 -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 21841 invoked from network); 9 Aug 2002 02:35:13 -0000 Received: from unknown (HELO localhost.redhat.com) (24.112.240.27) by sources.redhat.com with SMTP; 9 Aug 2002 02:35:13 -0000 Received: from ges.redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 351233F77; Thu, 8 Aug 2002 22:35:10 -0400 (EDT) Message-ID: <3D532A5E.7020706@ges.redhat.com> Date: Thu, 08 Aug 2002 19:35:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.0) Gecko/20020802 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Daniel Jacobowitz Cc: gdb-patches@sources.redhat.com Subject: Re: [patch/rfc] Don't include vector registers in ``info registers'' References: <3D53041D.90609@ges.redhat.com> <20020809013343.GA5331@nevyn.them.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-08/txt/msg00206.txt.bz2 > On Thu, Aug 08, 2002 at 07:51:57PM -0400, Andrew Cagney wrote: > >> Hello, >> >> The attached patch modifies the generic ``info registsters'' command so >> that it precludes vector registers (in addition to floating-point >> registers). The online doco indicates: >> >> (gdb) help info registers >> List of integer registers and their contents, for selected stack frame. >> Register name as argument means describe only that register. >> (gdb) help info all-registers >> List of all registers and their contents, for selected stack frame. >> Register name as argument means describe only that register. >> >> I think the change makes the behavour a better match for both the >> documentation and what I think is the intent of the command. Print a >> minimal set of registers. >> >> It will eventually affect the i386 -- I've a patch to change the type of >> xmm [and mmx] registers to true vectors. When that is in, ``info >> registers'' will stop displaying the xmm registers. >> >> Thoughts? > > > My only comment is that I would also like ``info registers'' not to > print kernel-mode or processor status registers, since that seems (to > me) to be appropriate; it should print registers for stack/pc and > computation primarily, not things like the MSR. Yes. There has been talk of adding a register attribute function. I suspect, though, that the function is of more use to GUI's then the CLI. > Might be harder to do generically though. Yes. I suspect the reality is that every architecture will eventually ends up with a custom info-registers function. Simply because they want the output to be something useful. Might even end up doing this for the i386. I think we need to be careful to not fall into the trap of over engineering the default function. Instead, encourage each target to do it custom but do provide some useful register print routines. -- Thinking out loud. Perhaphs the default ``info float[-registers]'' should scan for and print any floating-point registers and only print ``no float'' if none are found. enjoy, Andrew