From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31246 invoked by alias); 26 Oct 2007 19:26:19 -0000 Received: (qmail 31234 invoked by uid 22791); 26 Oct 2007 19:26:18 -0000 X-Spam-Check-By: sourceware.org Received: from igw2.br.ibm.com (HELO igw2.br.ibm.com) (32.104.18.25) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 26 Oct 2007 19:26:15 +0000 Received: from mailhub1.br.ibm.com (mailhub1 [9.18.232.109]) by igw2.br.ibm.com (Postfix) with ESMTP id 8A14917F482 for ; Fri, 26 Oct 2007 17:23:31 -0200 (BRDT) Received: from d24av02.br.ibm.com (d24av02.br.ibm.com [9.18.232.47]) by mailhub1.br.ibm.com (8.13.8/8.13.8/NCO v8.5) with ESMTP id l9QJQ9BX1458224 for ; Fri, 26 Oct 2007 17:26:10 -0200 Received: from d24av02.br.ibm.com (loopback [127.0.0.1]) by d24av02.br.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id l9QJQ7dc014599 for ; Fri, 26 Oct 2007 16:26:07 -0300 Received: from [9.18.198.192] ([9.18.198.192]) by d24av02.br.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id l9QJQ5dK014389 for ; Fri, 26 Oct 2007 16:26:06 -0300 Message-ID: <47223F51.4010309@linux.vnet.ibm.com> Date: Fri, 26 Oct 2007 22:14:00 -0000 From: Carlos Eduardo Seo User-Agent: Thunderbird 2.0.0.6 (X11/20070907) MIME-Version: 1.0 To: GDB Patches Mailing List Subject: [RFC] Add support for PPC Altivec registers in gcore OpenPGP: id=8BFFA900 Content-Type: multipart/mixed; boundary="------------010408080308030308010903" 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 X-SW-Source: 2007-10/txt/msg00721.txt.bz2 This is a multi-part message in MIME format. --------------010408080308030308010903 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-length: 706 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The attached patch makes gcore dump the contents of PPC Altivec registers. However, I'm not happy with declaring a bunch of PPC-specific stuff in gregset.h. But since FPXREGSET was there, I put everything in that file as well. I'm open to comments about how to make this better, so please give me some thoughts. Thanks and regards, - -- Carlos Eduardo Seo Software Engineer IBM Linux Technology Center -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHIj9Qqvq7Aov/qQARAqynAJ4yaW/b7X0jloBCvIluJmZZWP8jpQCff44Z suYd5ULIiP5pXvSnhyjX/T0= =qmI6 -----END PGP SIGNATURE----- --------------010408080308030308010903 Content-Type: text/x-patch; name="gcore-altivec.diff" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="gcore-altivec.diff" Content-length: 4806 2007-10-26 Carlos Eduardo Seo * linux-nat.c (linux_nat_do_thread_registers): Added support for PPC Altivec registers. * ppc-linux-nat.c: Removed definitions of SIZEOF_VRREGS and gdb_vrregset_t. * gregset.h: Added definitions of SIZEOF_VRREGS and gdb_vrregset_t. (fill_vrregset): Declare. Index: src/gdb/linux-nat.c =================================================================== --- src.orig/gdb/linux-nat.c +++ src/gdb/linux-nat.c @@ -2616,6 +2616,7 @@ linux_nat_do_thread_registers (bfd *obfd { gdb_gregset_t gregs; gdb_fpregset_t fpregs; + gdb_vrregset_t vrregs; #ifdef FILL_FPXREGSET gdb_fpxregset_t fpxregs; #endif @@ -2676,6 +2677,21 @@ linux_nat_do_thread_registers (bfd *obfd note_size, &fpxregs, sizeof (fpxregs)); #endif + + if (core_regset_p + && (regset = gdbarch_regset_from_core_section (gdbarch, ".reg-ppc-vmx", + sizeof (vrregs))) != NULL + && regset->collect_regset != NULL) + regset->collect_regset (regset, regcache, -1, + &vrregs, sizeof (vrregs)); + else + fill_vrregset (regcache, &vrregs); + + note_data = (char *) elfcore_write_ppc_vmx (obfd, + note_data, + note_size, + &vrregs, sizeof (vrregs)); + return note_data; } Index: src/gdb/ppc-linux-nat.c =================================================================== --- src.orig/gdb/ppc-linux-nat.c +++ src/gdb/ppc-linux-nat.c @@ -79,38 +79,6 @@ #define PTRACE_GETSIGINFO 0x4202 #endif -/* This oddity is because the Linux kernel defines elf_vrregset_t as - an array of 33 16 bytes long elements. I.e. it leaves out vrsave. - However the PTRACE_GETVRREGS and PTRACE_SETVRREGS requests return - the vrsave as an extra 4 bytes at the end. I opted for creating a - flat array of chars, so that it is easier to manipulate for gdb. - - There are 32 vector registers 16 bytes longs, plus a VSCR register - which is only 4 bytes long, but is fetched as a 16 bytes - quantity. Up to here we have the elf_vrregset_t structure. - Appended to this there is space for the VRSAVE register: 4 bytes. - Even though this vrsave register is not included in the regset - typedef, it is handled by the ptrace requests. - - Note that GNU/Linux doesn't support little endian PPC hardware, - therefore the offset at which the real value of the VSCR register - is located will be always 12 bytes. - - The layout is like this (where x is the actual value of the vscr reg): */ - -/* *INDENT-OFF* */ -/* - |.|.|.|.|.....|.|.|.|.||.|.|.|x||.| - <-------> <-------><-------><-> - VR0 VR31 VSCR VRSAVE -*/ -/* *INDENT-ON* */ - -#define SIZEOF_VRREGS 33*16+4 - -typedef char gdb_vrregset_t[SIZEOF_VRREGS]; - - /* On PPC processors that support the the Signal Processing Extension (SPE) APU, the general-purpose registers are 64 bits long. However, the ordinary Linux kernel PTRACE_PEEKUSER / PTRACE_POKEUSER @@ -687,7 +655,7 @@ store_register (const struct regcache *r } } -static void +void fill_vrregset (const struct regcache *regcache, gdb_vrregset_t *vrregsetp) { int i; Index: src/gdb/gregset.h =================================================================== --- src.orig/gdb/gregset.h +++ src/gdb/gregset.h @@ -72,4 +72,40 @@ extern void fill_fpxregset (const struct gdb_fpxregset_t *fpxregs, int regno); #endif +/* For PPC Altivec support */ + +/* This oddity is because the Linux kernel defines elf_vrregset_t as + an array of 33 16 bytes long elements. I.e. it leaves out vrsave. + However the PTRACE_GETVRREGS and PTRACE_SETVRREGS requests return + the vrsave as an extra 4 bytes at the end. I opted for creating a + flat array of chars, so that it is easier to manipulate for gdb. + + There are 32 vector registers 16 bytes longs, plus a VSCR register + which is only 4 bytes long, but is fetched as a 16 bytes + quantity. Up to here we have the elf_vrregset_t structure. + Appended to this there is space for the VRSAVE register: 4 bytes. + Even though this vrsave register is not included in the regset + typedef, it is handled by the ptrace requests. + + Note that GNU/Linux doesn't support little endian PPC hardware, + therefore the offset at which the real value of the VSCR register + is located will be always 12 bytes. + + The layout is like this (where x is the actual value of the vscr reg): */ + +/* *INDENT-OFF* */ +/* + |.|.|.|.|.....|.|.|.|.||.|.|.|x||.| + <-------> <-------><-------><-> + VR0 VR31 VSCR VRSAVE +*/ +/* *INDENT-ON* */ + +#define SIZEOF_VRREGS 33*16+4 + +typedef char gdb_vrregset_t[SIZEOF_VRREGS]; + +extern void +fill_vrregset (const struct regcache *regcache, gdb_vrregset_t *vrregsetp); + #endif --------------010408080308030308010903 Content-Type: application/octet-stream; name="gcore-altivec.diff.sig" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="gcore-altivec.diff.sig" Content-length: 90 iD4DBQBHIj9Qqvq7Aov/qQARAtOAAJ9bXtT93p1HQVvxTpptgfnhlTFEvQCX R8SklKYQyv1xOqS+xmAzp0dHYw== --------------010408080308030308010903--