From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7149 invoked by alias); 30 Oct 2002 14:09:31 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 7015 invoked from network); 30 Oct 2002 14:09:28 -0000 Received: from unknown (HELO localhost.redhat.com) (66.187.233.200) by sources.redhat.com with SMTP; 30 Oct 2002 14:09:28 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id E82B23C57; Wed, 30 Oct 2002 09:09:26 -0500 (EST) Message-ID: <3DBFE816.4050801@redhat.com> Date: Wed, 30 Oct 2002 06:09:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.0) Gecko/20020824 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Romain Berrendonner Cc: gdb@sources.redhat.com Subject: Re: set processor command References: <20021029100028.GA1212@torino.act-europe.fr> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-10/txt/msg00199.txt.bz2 > Hi folks, > > I did a small comparison between gdb 5.0, 5.1 and gdb 5.2.1 (configured as > --target=powerpc-unknown-elf, solaris hosted) regarding the 'set processor' > command. The output is: > > gdb 5.0: > -------- > GDB knows about the following PowerPC and RS6000 variants: > ppc-uisa PowerPC UISA - a PPC processor as viewed by user-level code > rs6000 IBM RS6000 ("POWER") architecture, user-level view > 403 IBM PowerPC 403 > 403GC IBM PowerPC 403GC > 505 Motorola PowerPC 505 > 860 Motorola PowerPC 860 or 850 > 601 Motorola PowerPC 601 > 602 Motorola PowerPC 602 > 603 Motorola/IBM PowerPC 603 or 603e > 604 Motorola PowerPC 604 or 604e > 750 Motorola/IBM PowerPC 750 or 740 > > gdb 5.1: > -------- > Requires an argument. Valid arguments are rs6000:6000, rs6000:rs1, rs6000:rsc, rs6000:rs2, powerpc:common, powerpc:603, powerpc:EC603e, powerpc:604, powerpc:403, powerpc:601, powerpc:620, powerpc:630, powerpc:a35, powerpc:rs64ii, powerpc:rs64iii, powerpc:7400, powerpc:MPC8XX, auto. > > gdb 5.2.1: > ---------- > Requires an argument. Valid arguments are rs6000:6000, rs6000:rs1, rs6000:rsc, rs6000:rs2, powerpc:common, auto. > > As you may see, the definition of the variants of powerpc vary considerably > from one version to another, and I would like to know what will be the > futur of this command: it looks like it is being deprecated, with less and > less variants supported. Is that true ? Or is it only that the existing code > is more generic ? The code was rationalied (across a number of architectures) and also made very generic. GDB ``supports'' any architecture/machine that is both: - known by bfd - known by gdb It's included in the list. The names are obtained via a query to BFD. A useful new feature (BFD and GDB) might be to also obtain a brief description of the architecture/machine. Andrew