From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15358 invoked by alias); 12 Oct 2002 09:01:26 -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 15315 invoked from network); 12 Oct 2002 09:01:25 -0000 Received: from unknown (HELO balder.inter.net.il) (192.114.186.15) by sources.redhat.com with SMTP; 12 Oct 2002 09:01:25 -0000 Received: from Zaretsky ([80.230.7.145]) by balder.inter.net.il (Mirapoint Messaging Server MOS 3.1.0.58-GA) with ESMTP id BVC42355; Sat, 12 Oct 2002 11:01:18 +0200 (IST) Date: Sat, 12 Oct 2002 02:01:00 -0000 From: "Eli Zaretskii" To: klee@apple.com Message-Id: <1438-Sat12Oct2002105650+0200-eliz@is.elta.co.il> CC: gdb-patches@sources.redhat.com In-reply-to: <22199F8A-DD36-11D6-B6D6-00039396EEB8@apple.com> (message from Klee Dienes on Fri, 11 Oct 2002 12:26:02 -0400) Subject: Re: [PATCH] Print vector registers in natural format, not hex Reply-to: Eli Zaretskii References: <22199F8A-DD36-11D6-B6D6-00039396EEB8@apple.com> X-SW-Source: 2002-10/txt/msg00248.txt.bz2 > Date: Fri, 11 Oct 2002 12:26:02 -0400 > From: Klee Dienes > > Maybe something along the lines of: > > @value{GDBN} always considers the contents of an ordinary register as an > integer when the register is examined in this way. Some machines have > special registers that are predefined to have specific types (typically > floating > point or vector registers); these registers are printed according to > their > system-defined type. There is no way to refer to the contents of an > ordinary > register as a floating point value or vector type (although you can > @emph{print} > it as a floating point value with @samp{print/f $@var{regname}}). That's good, but perhaps an explicit reference to "info vector" and "info float" would be useful.