From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31609 invoked by alias); 9 Aug 2002 01:45:46 -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 31602 invoked from network); 9 Aug 2002 01:45:44 -0000 Received: from unknown (HELO cygnus.com) (205.180.83.203) by sources.redhat.com with SMTP; 9 Aug 2002 01:45:44 -0000 Received: from redhat.com (reddwarf.sfbay.redhat.com [172.16.24.50]) by runyon.cygnus.com (8.8.7-cygnus/8.8.7) with ESMTP id SAA08437; Thu, 8 Aug 2002 18:43:20 -0700 (PDT) Message-ID: <3D531A59.96D86F43@redhat.com> Date: Thu, 08 Aug 2002 18:45:00 -0000 From: Michael Snyder Organization: Red Hat, Inc. X-Accept-Language: en MIME-Version: 1.0 To: Daniel Jacobowitz CC: Andrew Cagney , 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 Content-Transfer-Encoding: 7bit X-SW-Source: 2002-08/txt/msg00201.txt.bz2 Daniel Jacobowitz wrote: > > 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. > > Might be harder to do generically though. That would mean that in order to see things like the status and control registers, you would have to do info all-reg, which would then spit out all your FP and VEC registers too. Folks who need the in-between registers might not like that.