From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20115 invoked by alias); 4 Mar 2010 21:59:54 -0000 Received: (qmail 20107 invoked by uid 22791); 4 Mar 2010 21:59:54 -0000 X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (38.113.113.100) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 04 Mar 2010 21:59:50 +0000 Received: (qmail 27358 invoked from network); 4 Mar 2010 21:59:48 -0000 Received: from unknown (HELO localhost) (froydnj@127.0.0.2) by mail.codesourcery.com with ESMTPA; 4 Mar 2010 21:59:48 -0000 Date: Thu, 04 Mar 2010 21:59:00 -0000 From: Nathan Froyd To: "H.J. Lu" Cc: GDB Subject: Re: PATCH: 1/6: Add AVX support Message-ID: <20100304215948.GK16726@codesourcery.com> References: <20100304180219.GA10826@intel.com> <20100304190934.GB15979@caradoc.them.org> <6dc9ffc81003041129i72a8a79bn66721fecc7b6a83b@mail.gmail.com> <20100304194645.GA20453@caradoc.them.org> <6dc9ffc81003041327m379c6903g571f4d66aac8d61a@mail.gmail.com> <20100304213415.GJ16726@codesourcery.com> <6dc9ffc81003041341r33f5a878uf0540ef69d8fc843@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <6dc9ffc81003041341r33f5a878uf0540ef69d8fc843@mail.gmail.com> User-Agent: Mutt/1.5.17+20080114 (2008-01-14) 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: 2010-03/txt/msg00218.txt.bz2 On Thu, Mar 04, 2010 at 01:41:05PM -0800, H.J. Lu wrote: > On Thu, Mar 4, 2010 at 1:34 PM, Nathan Froyd wrote: > > On Thu, Mar 04, 2010 at 01:27:09PM -0800, H.J. Lu wrote: > >> Your description only works for truly NEW registers, which > >> AVX registers aren't.  AVX registers are actually the old SSE > >> registers with different names. > > > > You can make "wide" registers like this work; the PPC backend does this > > for the SPE registers, where the lower 32 bits function as the normal > > PPC registers and the upper 32 bits are sent as separate "registers". > > GDB then synthesizes the complete register out of both parts. > > I am not familiar with SPE. How does it work with native SPE > gdb? Does it support old registers with new names? I assume it works just fine; I've never taken the chance to see how it works natively, but it works just fine remotely. Of course, the native bits have to be written with an understanding of how the high parts of the registers work. I don't understand your second question. -Nathan