From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7294 invoked by alias); 5 Mar 2009 23:08:09 -0000 Received: (qmail 7283 invoked by uid 22791); 5 Mar 2009 23:08:08 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 05 Mar 2009 23:08:02 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id 27B70107CF; Thu, 5 Mar 2009 23:08:00 +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 043F810514; Thu, 5 Mar 2009 23:07:59 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1LfMfX-0004tT-3W; Thu, 05 Mar 2009 18:07:59 -0500 Date: Thu, 05 Mar 2009 23:08:00 -0000 From: Daniel Jacobowitz To: Joel Brobecker Cc: gdb-patches@sourceware.org Subject: Re: [patch] mips-tdep: info registers Message-ID: <20090305230759.GA18795@caradoc.them.org> Mail-Followup-To: Joel Brobecker , gdb-patches@sourceware.org References: <20090223162602.GH26056@adacore.com> <20090227195607.GJ26056@adacore.com> <20090305191245.GB3744@adacore.com> <20090305192211.GA2342@caradoc.them.org> <20090305193512.GB3070@caradoc.them.org> <20090305225030.GD3744@adacore.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090305225030.GD3744@adacore.com> 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 Mail-Followup-To: gdb-patches@sourceware.org X-SW-Source: 2009-03/txt/msg00068.txt.bz2 On Thu, Mar 05, 2009 at 02:50:30PM -0800, Joel Brobecker wrote: > > 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. Or change how info registers works, perhaps. -- Daniel Jacobowitz CodeSourcery