From mboxrd@z Thu Jan 1 00:00:00 1970 From: Elena Zannoni To: Kevin Buettner Cc: Andrew Cagney , Elena Zannoni , Daniel Jacobowitz , gdb-patches@sources.redhat.com Subject: Re: [RFA] W.I.P. AltiVec ppc registers support. Date: Thu, 29 Nov 2001 16:36:00 -0000 Message-id: <15366.54795.679235.961389@krustylu.cygnus.com> References: <15365.39495.801289.497931@krustylu.cygnus.com> <1011129183830.ZM18856@ocotillo.lan> <15366.44991.616576.411278@krustylu.cygnus.com> <1011129222000.ZM19585@ocotillo.lan> <15366.47960.711736.518863@krustylu.cygnus.com> <3C06BED3.4070209@cygnus.com> <1011130002533.ZM20054@ocotillo.lan> X-SW-Source: 2001-11/msg00591.html Kevin Buettner writes: > On Nov 29, 6:03pm, Andrew Cagney wrote: > > > >> Unfortunately not. I thought the same, until I remembered about core > > > > > file debugging. That function is called by fetch_core_registers() in > > > > > core-aout.c. > > > > > Hmm... I wonder if Linux/PPC even needs this function in core-aout.c. > > > > Daniel J. is the expert on this stuff. Daniel, doesn't Linux/PPC use > > > > core-regset.c instead? > > > > Whoops, yes, you are right. False alarm. > > > > So just the core code needs to have a hard-wired (non native header) way > > of unpacking Altivec registers (if they are found?)? > > I'm guessing we'll end up having to add fetch_core_registers() and > company to ppc-linux-nat.c. That way neither core-regset.c nor > core-aout.c will be used for a native Linux/PPC build. (See > fetch_core_registers() in i386-linux-nat.c as an example.) cross core file support: is that a concern? Side bar: there is something interesting about the way the corelow.c file gets the registers sections from a core file. It looks for .reg (gregs), .reg2 (fpregs), and .reg-xfp (extended-floating point x86 only(?)). Seems like I'll have to add a fetch section call for a .reg-altivec (or whatever it will be called, it's not produced yet). But that's in common code. I don't like it. This get_core_registers() will have to be overwritten too, maybe. Elena > > Kevin From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31580 invoked by alias); 30 Nov 2001 00:36:40 -0000 Mailing-List: contact gdb-patches-help@sourceware.cygnus.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 31559 invoked from network); 30 Nov 2001 00:36:39 -0000 Received: from unknown (HELO cygnus.com) (205.180.230.5) by hostedprojects.ges.redhat.com with SMTP; 30 Nov 2001 00:36:39 -0000 Received: from rtl.cygnus.com (cse.cygnus.com [205.180.230.236]) by runyon.cygnus.com (8.8.7-cygnus/8.8.7) with ESMTP id QAA26435; Thu, 29 Nov 2001 16:36:34 -0800 (PST) Received: (from ezannoni@localhost) by rtl.cygnus.com (8.11.2/8.11.0) id fAU0gpx04205; Thu, 29 Nov 2001 19:42:51 -0500 X-Authentication-Warning: krustylu.cygnus.com: ezannoni set sender to ezannoni@cygnus.com using -f From: Elena Zannoni MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15366.54795.679235.961389@krustylu.cygnus.com> Date: Tue, 20 Nov 2001 16:10:00 -0000 To: Kevin Buettner Cc: Andrew Cagney , Elena Zannoni , Daniel Jacobowitz , gdb-patches@sources.redhat.com Subject: Re: [RFA] W.I.P. AltiVec ppc registers support. In-Reply-To: <1011130002533.ZM20054@ocotillo.lan> References: <15365.39495.801289.497931@krustylu.cygnus.com> <1011129183830.ZM18856@ocotillo.lan> <15366.44991.616576.411278@krustylu.cygnus.com> <1011129222000.ZM19585@ocotillo.lan> <15366.47960.711736.518863@krustylu.cygnus.com> <3C06BED3.4070209@cygnus.com> <1011130002533.ZM20054@ocotillo.lan> X-Mailer: VM 6.97 under Emacs 20.7.1 X-SW-Source: 2001-11/txt/msg00376.txt.bz2 Message-ID: <20011120161000.F-tu0_m6G9fzzUbGTsVT4XSq3phv8HibP54gVRP017g@z> Kevin Buettner writes: > On Nov 29, 6:03pm, Andrew Cagney wrote: > > > >> Unfortunately not. I thought the same, until I remembered about core > > > > > file debugging. That function is called by fetch_core_registers() in > > > > > core-aout.c. > > > > > Hmm... I wonder if Linux/PPC even needs this function in core-aout.c. > > > > Daniel J. is the expert on this stuff. Daniel, doesn't Linux/PPC use > > > > core-regset.c instead? > > > > Whoops, yes, you are right. False alarm. > > > > So just the core code needs to have a hard-wired (non native header) way > > of unpacking Altivec registers (if they are found?)? > > I'm guessing we'll end up having to add fetch_core_registers() and > company to ppc-linux-nat.c. That way neither core-regset.c nor > core-aout.c will be used for a native Linux/PPC build. (See > fetch_core_registers() in i386-linux-nat.c as an example.) cross core file support: is that a concern? Side bar: there is something interesting about the way the corelow.c file gets the registers sections from a core file. It looks for .reg (gregs), .reg2 (fpregs), and .reg-xfp (extended-floating point x86 only(?)). Seems like I'll have to add a fetch section call for a .reg-altivec (or whatever it will be called, it's not produced yet). But that's in common code. I don't like it. This get_core_registers() will have to be overwritten too, maybe. Elena > > Kevin