From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13896 invoked by alias); 27 Oct 2005 15:35:56 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 13865 invoked by uid 22791); 27 Oct 2005 15:35:47 -0000 Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Thu, 27 Oct 2005 15:35:47 +0000 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1EV9n7-0006YB-MT for gdb@sources.redhat.com; Thu, 27 Oct 2005 11:35:45 -0400 Date: Thu, 27 Oct 2005 15:35:00 -0000 From: Daniel Jacobowitz To: gdb@sources.redhat.com Subject: Re: PowerPC 603 Register Set Clarification Message-ID: <20051027153545.GA25150@nevyn.them.org> Mail-Followup-To: gdb@sources.redhat.com References: <20051027025856.GD6186@Power-Mac-G5.local> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051027025856.GD6186@Power-Mac-G5.local> User-Agent: Mutt/1.5.8i X-SW-Source: 2005-10/txt/msg00166.txt.bz2 On Wed, Oct 26, 2005 at 10:58:56PM -0400, Ron McCall wrote: > Hi, > > I am unsure as to how to handle the ASR register and the two placeholder > registers that are defined for the PowerPC 603 with respect to the 'g' > and 'G' packets and was hoping someone could clarify it for me. I am > currently working with GDB 6.3.50.20051026. > > In rs6000-tdep.c, PPC_OEA_SPRS includes the ASR register which is > declared S64 (a 64-bit register on 64-bit systems that doesn't exist on > 32-bit systems). The 603 isn't 64-bit but the register still appears to > take up a register number nonetheless. Does it also take up space (16 > hex chars) in the 'G' packet, which is then intended to be skipped by > the stub? If so, should the stub then fill in zeroes for this register > in the 'g' packet? The best way to answer this question is to configure GDB appropriately to talk to a 603 target, and then run "maint info registers". That will tell you the expected offsets of every register. -- Daniel Jacobowitz CodeSourcery, LLC