From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11137 invoked by alias); 17 Nov 2008 22:19:23 -0000 Received: (qmail 11057 invoked by uid 22791); 17 Nov 2008 22:19:22 -0000 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 17 Nov 2008 22:18:43 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id ED11110DB0; Mon, 17 Nov 2008 22:18:40 +0000 (GMT) Received: from caradoc.them.org (209.195.188.212.nauticom.net [209.195.188.212]) by nan.false.org (Postfix) with ESMTP id AD60410D50; Mon, 17 Nov 2008 22:18:40 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1L2CQZ-0000fH-OM; Mon, 17 Nov 2008 17:18:39 -0500 Date: Tue, 18 Nov 2008 05:46:00 -0000 From: Daniel Jacobowitz To: Thiago Jung Bauermann Cc: Joel Brobecker , gdb-patches ml Subject: Re: [rfc][1/2] add suport for 64-bit fpscr in powerpc linux native Message-ID: <20081117221839.GA2536@caradoc.them.org> Mail-Followup-To: Thiago Jung Bauermann , Joel Brobecker , gdb-patches ml References: <1221436875.17278.4.camel@localhost.localdomain> <20081113235027.GA12484@adacore.com> <20081113235402.GA12802@adacore.com> <1226959224.28256.38.camel@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1226959224.28256.38.camel@localhost.localdomain> User-Agent: Mutt/1.5.17 (2008-05-11) X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2008-11/txt/msg00451.txt.bz2 On Mon, Nov 17, 2008 at 08:00:23PM -0200, Thiago Jung Bauermann wrote: > If linking to the expat library wasn't optional when building GDB, one > option would be to provide just the power-fpu-isa205.xml file containing > the feature description, and then generate the target description XML on > the fly including the appropriate features, and have GDB parse that. There's another way you could do it... if the individual features could be compiled to C instead of just entire descriptions you could call their generated functions. It's not set up to work that way at the moment. I don't know if it would be an easy change or a messy one. > > > +gdb_test "print/t \$fpscr" " = 10100000000000000000000000000000000" "FPSCR for round to nearest, ties toward zero rounding mode" > > > > Just a casual remark, not a request for change, but I'm surprised > > that you might find /t more useful in this case than /x ;-). > > I agree in general /x is more helpful, but in this case binary was > easier because the FPSCR is just a bunch of flags, so I could directly > see which were set and which weren't. > > Ok, I admit I still don't do my taxes in hex. :-) You do them in binary? Anyway, you might want to consider adding a flags type, like x86 %eflags, for $fpscr. -- Daniel Jacobowitz CodeSourcery