From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2175 invoked by alias); 30 Nov 2001 00:43:59 -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 2111 invoked from network); 30 Nov 2001 00:43:57 -0000 Received: from unknown (HELO localhost.cygnus.com) (216.138.202.10) by hostedprojects.ges.redhat.com with SMTP; 30 Nov 2001 00:43:57 -0000 Received: from cygnus.com (localhost [127.0.0.1]) by localhost.cygnus.com (Postfix) with ESMTP id 8B7203DE9; Thu, 29 Nov 2001 19:43:56 -0500 (EST) Message-ID: <3C06D64C.4030801@cygnus.com> Date: Tue, 20 Nov 2001 16:14:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:0.9.3) Gecko/20011020 X-Accept-Language: en-us MIME-Version: 1.0 To: Kevin Buettner Cc: Elena Zannoni , Daniel Jacobowitz , gdb-patches@sources.redhat.com Subject: Re: [RFA] W.I.P. AltiVec ppc registers support. 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> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2001-11/txt/msg00378.txt.bz2 >> 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.) No. The core stuff would need to be kicked out of *-nat.c and into *-core.c and/or *-greg.c and/or ??? The packing/unpacking of a reg-set is technically only target dependant - debugging a core file from an embedded target. Daniel, how are the changes you were eluding to comming along? Andrew From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cagney To: Kevin Buettner Cc: 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:43:00 -0000 Message-ID: <3C06D64C.4030801@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/msg00593.html Message-ID: <20011129164300.ckoNOKvv-hP8gDuaVq4KdNdCq6x1o_tmB9cKUElrToU@z> >> 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.) No. The core stuff would need to be kicked out of *-nat.c and into *-core.c and/or *-greg.c and/or ??? The packing/unpacking of a reg-set is technically only target dependant - debugging a core file from an embedded target. Daniel, how are the changes you were eluding to comming along? Andrew