From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31553 invoked by alias); 28 Mar 2010 16:40:55 -0000 Received: (qmail 31402 invoked by uid 22791); 28 Mar 2010 16:40:53 -0000 X-SWARE-Spam-Status: No, hits=-2.5 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; Sun, 28 Mar 2010 16:40:49 +0000 Received: (qmail 9510 invoked from network); 28 Mar 2010 16:40:48 -0000 Received: from unknown (HELO caradoc.them.org) (dan@127.0.0.2) by mail.codesourcery.com with ESMTPA; 28 Mar 2010 16:40:48 -0000 Date: Sun, 28 Mar 2010 16:40:00 -0000 From: Daniel Jacobowitz To: Pedro Alves Cc: gdb-patches@sourceware.org, "H.J. Lu" Subject: Re: PATCH: 6/6 [2nd try]: Add AVX support (gdbserver changes) Message-ID: <20100328164045.GB5815@caradoc.them.org> Mail-Followup-To: Pedro Alves , gdb-patches@sourceware.org, "H.J. Lu" References: <20100304180219.GA10826@intel.com> <20100327160705.GB16019@caradoc.them.org> <6dc9ffc81003271811t5be04ef9yf888edbce6d85236@mail.gmail.com> <201003280855.44473.pedro@codesourcery.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201003280855.44473.pedro@codesourcery.com> User-Agent: Mutt/1.5.20 (2009-06-14) 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/msg00947.txt.bz2 On Sun, Mar 28, 2010 at 07:55:44AM +0000, Pedro Alves wrote: > This (and the gdbarch_qsupported mechanism) worries me multi-arch > design wise. There's a bootstrapping problem here. GDB sends qSupported > to the target before knowing the target's target description. The target > sends the target description based on qSupported. > As is, things only work correctly, when GDB already somehow knows the > arch is some sort of x86 _before_ connecting to the target. That's > usually true if you give GDB a binary, but may not be true in some > use cases. You're right. I forgot about this; the design won't work. Would "xmlRegisters=arm,x86" be a better solution? If so, the way to implement that is to have a registration function. i386-tdep.c:_initialize_i386_tdep can call a function in remote.c to add "x86" to the list of xmlRegisters architectures. -- Daniel Jacobowitz CodeSourcery