From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1490 invoked by alias); 20 Apr 2008 14:28:13 -0000 Received: (qmail 1482 invoked by uid 22791); 20 Apr 2008 14:28:12 -0000 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sun, 20 Apr 2008 14:27:53 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id BDC83983E5; Sun, 20 Apr 2008 14:27:51 +0000 (GMT) Received: from caradoc.them.org (22.svnf5.xdsl.nauticom.net [209.195.183.55]) by nan.false.org (Postfix) with ESMTP id 9D83498150; Sun, 20 Apr 2008 14:27:51 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1JnaWE-0006PU-UT; Sun, 20 Apr 2008 10:27:50 -0400 Date: Mon, 21 Apr 2008 09:21:00 -0000 From: Daniel Jacobowitz To: Thiago Jung Bauermann Cc: Ulrich Weigand , gdb-patches@sourceware.org Subject: Re: [rfc/rft] ppc gdbserver: autodetect AltiVec and SPE Message-ID: <20080420142750.GA24305@caradoc.them.org> Mail-Followup-To: Thiago Jung Bauermann , Ulrich Weigand , gdb-patches@sourceware.org References: <200803262021.m2QKLTWs019049@d12av02.megacenter.de.ibm.com> <1208563645.5808.90.camel@localhost.localdomain> <20080419035837.GB22517@caradoc.them.org> <1208667119.5808.126.camel@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1208667119.5808.126.camel@localhost.localdomain> User-Agent: Mutt/1.5.17 (2007-12-11) 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-04/txt/msg00420.txt.bz2 On Sun, Apr 20, 2008 at 01:51:59AM -0300, Thiago Jung Bauermann wrote: > No, it was a clean build. I got what's happening. The patch removed > powerpc-e500.o from powerpc64-*-linux*, because e500 is 32-bit only. The > call to init_registers_powerpc_e500 is protected by an #ifndef > __powerpc64__, so it shouldn't be a problem. But in practice it is, > because when using plain "../src/configure && make" in a ppc64 machine > with a 32-bit default gcc, the target is autodetected to be > powerpc64-unknown-linux-gnu. Thus, that call to > init_registers_powerpc_e500 will be compiled in (it's a 32 bit > compilation), but powerpc-e500.o won't be included (it's a powerpc64 > target). > > Is such way of compiling 32-bit GDB in a ppc64 machine with 32-bit > default gcc not supported? Must one always use --target option to > configure in such case? I see. Anything is supported that we're willing to fix... The simplest possible fix would be to add the e500 objects. Does gdbserver work OK with this patch? -- Daniel Jacobowitz CodeSourcery 2008-04-20 Daniel Jacobowitz * configure.srv: Add e500 objects even for powerpc64. Index: configure.srv =================================================================== RCS file: /cvs/src/src/gdb/gdbserver/configure.srv,v retrieving revision 1.33 diff -u -p -r1.33 configure.srv --- configure.srv 17 Apr 2008 21:22:41 -0000 1.33 +++ configure.srv 20 Apr 2008 14:27:03 -0000 @@ -106,7 +106,7 @@ case "${target}" in srv_linux_usrregs=yes srv_linux_thread_db=yes ;; - powerpc64-*-linux*) srv_regobj="reg-ppc.o powerpc-32.o" + powerpc64-*-linux*) srv_regobj="reg-ppc.o powerpc-32.o powerpc-e500.o" srv_regobj="${srv_regobj} reg-ppc64.o powerpc-64.o" srv_tgtobj="linux-low.o linux-ppc-low.o" srv_xmlfiles="rs6000/powerpc-32.xml" @@ -115,6 +115,8 @@ case "${target}" in srv_xmlfiles="${srv_xmlfiles} rs6000/power-fpu.xml" srv_xmlfiles="${srv_xmlfiles} rs6000/powerpc-64.xml" srv_xmlfiles="${srv_xmlfiles} rs6000/power64-core.xml" + srv_xmlfiles="${srv_xmlfiles} rs6000/powerpc-e500.xml" + srv_xmlfiles="${srv_xmlfiles} rs6000/power-spe.xml" srv_linux_usrregs=yes srv_linux_regsets=yes srv_linux_thread_db=yes