From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25013 invoked by alias); 25 Jul 2008 21:30:11 -0000 Received: (qmail 25000 invoked by uid 22791); 25 Jul 2008 21:30:10 -0000 X-Spam-Check-By: sourceware.org Received: from igw3.br.ibm.com (HELO igw3.br.ibm.com) (32.104.18.26) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 25 Jul 2008 21:29:43 +0000 Received: from mailhub3.br.ibm.com (unknown [9.18.232.110]) by igw3.br.ibm.com (Postfix) with ESMTP id 1682F3900BB for ; Fri, 25 Jul 2008 18:10:58 -0300 (BRST) Received: from d24av02.br.ibm.com (d24av02.br.ibm.com [9.18.232.47]) by mailhub3.br.ibm.com (8.13.8/8.13.8/NCO v8.7) with ESMTP id m6PLTeK42117742 for ; Fri, 25 Jul 2008 18:29:40 -0300 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 m6PLTZfx007895 for ; Fri, 25 Jul 2008 18:29:35 -0300 Received: from [9.18.202.49] ([9.18.202.49]) by d24av02.br.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id m6PLTYOL007290; Fri, 25 Jul 2008 18:29:34 -0300 Subject: Re: [PATCH-ppc 0/5] Add feature description for new VSX register set From: Thiago Jung Bauermann To: "Joseph S. Myers" Cc: Luis Machado , gdb-patches@sourceware.org In-Reply-To: References: <1217016935.29012.74.camel@gargoyle> Content-Type: text/plain Date: Fri, 25 Jul 2008 21:30:00 -0000 Message-Id: <1217021353.5922.121.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 Content-Transfer-Encoding: 7bit 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: 2008-07/txt/msg00456.txt.bz2 On Fri, 2008-07-25 at 21:01 +0000, Joseph S. Myers wrote: > On Fri, 25 Jul 2008, Luis Machado wrote: > > This is a patch series to enable POWER7 VSX register set support in GDB. > > The VSX registers' layout is as follows: > > Will IBM be making appropriate proposals regarding these registers in the > Power.org ABI working group? The obvious things that need defining > include DWARF debug/unwind information handling of the registers, and > what's call-saved / call-clobbered, plus ABI handling of any new > C-language datatypes. Regarding call-saved / call-clobbered there's no option really. VSX registers follow the saved-ness of the registers they overlap with (either floating point or altivec). Regarding the other points, I assume so. :-) We can ask around here, to double-check. -- []'s Thiago Jung Bauermann Software Engineer IBM Linux Technology Center