From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29564 invoked by alias); 5 Mar 2009 22:50:40 -0000 Received: (qmail 29556 invoked by uid 22791); 5 Mar 2009 22:50:40 -0000 X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 05 Mar 2009 22:50:34 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 64AB42BABE7 for ; Thu, 5 Mar 2009 17:50:36 -0500 (EST) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id y1YDv1GOtuUd for ; Thu, 5 Mar 2009 17:50:36 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 305CC2BABE6 for ; Thu, 5 Mar 2009 17:50:36 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id C787CE7ACD; Thu, 5 Mar 2009 14:50:30 -0800 (PST) Date: Thu, 05 Mar 2009 22:50:00 -0000 From: Joel Brobecker To: gdb-patches@sourceware.org Subject: Re: [patch] mips-tdep: info registers Message-ID: <20090305225030.GD3744@adacore.com> References: <20090223161756.GA19411@caradoc.them.org> <20090223162602.GH26056@adacore.com> <20090227195607.GJ26056@adacore.com> <20090305191245.GB3744@adacore.com> <20090305192211.GA2342@caradoc.them.org> <20090305193512.GB3070@caradoc.them.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090305193512.GB3070@caradoc.them.org> User-Agent: Mutt/1.4.2.2i 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 Mail-Followup-To: gdb-patches@sourceware.org X-SW-Source: 2009-03/txt/msg00067.txt.bz2 Daniel, Thanks for taking a look - I knew there was a reason I wasn't comfortable with this approach... > They should be aliases for the normal registers, e.g. $1 and $at > should mean the same thing. I have never implemented something like this before. How would you do it? I see that mips-tdep.c already has some table of register name aliases. This doesn't look like it can be connected to the "info registers" command, because of the way this command is implemented (it iterates over all register numbers, gets their associated names, and compares with the name used by the user). As far as I can tell, the only way that I can see is by adding a new series of pseudo-registers. -- Joel