From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7732 invoked by alias); 1 Apr 2008 20:23:11 -0000 Received: (qmail 7719 invoked by uid 22791); 1 Apr 2008 20:23:10 -0000 X-Spam-Check-By: sourceware.org Received: from az33egw02.freescale.net (HELO az33egw02.freescale.net) (192.88.158.103) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 01 Apr 2008 20:22:12 +0000 Received: from az33smr01.freescale.net (az33smr01.freescale.net [10.64.34.199]) by az33egw02.freescale.net (8.12.11/az33egw02) with ESMTP id m31KM6xW021766; Tue, 1 Apr 2008 13:22:06 -0700 (MST) Received: from ld0159-tx32 (ld0159-tx32.am.freescale.net [10.82.19.109]) by az33smr01.freescale.net (8.13.1/8.13.0) with ESMTP id m31KM5Fb007944; Tue, 1 Apr 2008 15:22:05 -0500 (CDT) Date: Tue, 01 Apr 2008 20:23:00 -0000 From: "Anmol P. Paralkar" To: Daniel Jacobowitz cc: gdb@sourceware.org Subject: Re: Regenerate config/features/rs6000 In-Reply-To: <20080401171247.GA26455@caradoc.them.org> Message-ID: References: <47F16D39.4040608@eagercon.com> <20080331234135.GA29623@caradoc.them.org> <47F17A97.1000408@eagercon.com> <20080401010823.GA1649@caradoc.them.org> <20080401171247.GA26455@caradoc.them.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2008-04/txt/msg00007.txt.bz2 On Tue, 1 Apr 2008, Daniel Jacobowitz wrote: > On Tue, Apr 01, 2008 at 12:07:16PM -0500, Anmol P. Paralkar wrote: >> Assume that you are adding support for 'newarch' (say under powerpc). > > Why do you even need this? Only in the instance of a truly brand new architecture? > You should be able to generate the C file > from an existing PowerPC even before teaching it about the new > architecture variant. If that doesn't work then you can't provide > new variants over remote, which would defeat the point. If there was > an error, please let me know. Sure, yes. That is not a problem e.g. powerpc-603.xml where, I suppose the variation is indicated by : ... > Meanwhile, I'd love to remove the circular dependency, but I haven't > thought of a way to do it yet. When you say circular dependency, you mean using a GDB to generate a part of itself, right? For variants of existing architecures this not so non-intuitive. However, when adding a brand new arch. (e.g. say if we had XML descriptions in place and were adding support for the e500), one has to teach it about the new architecture first, else it's not going to like the: powerpc:e500 resulting in: warning: while parsing target description (at line ): Target description specified unknown architecture "powerpc:e500" warning: Could not load XML target description; ignoring There is no target description to print. For a situation like that, is there a simpler process than/alternative to the one I outlined in my previous mail? Thanks, Anmol. > > -- > Daniel Jacobowitz > CodeSourcery >