From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1205 invoked by alias); 29 Oct 2003 19:30:15 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 1192 invoked from network); 29 Oct 2003 19:30:14 -0000 Received: from unknown (HELO localhost.redhat.com) (207.219.125.105) by sources.redhat.com with SMTP; 29 Oct 2003 19:30:14 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 5F75F2B89; Wed, 29 Oct 2003 14:30:13 -0500 (EST) Message-ID: <3FA01545.4070609@redhat.com> Date: Wed, 29 Oct 2003 19:30:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030820 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kevin Buettner Cc: Andrew Cagney , gdb-patches@sources.redhat.com Subject: Re: [patch/rfc,rfa:ppc64] Add osabi wildcard support References: <3F986371.9060708@redhat.com> <1031028215919.ZM3764@localhost.localdomain> <3F9DB049.10603@redhat.com> <1031029033241.ZM4676@localhost.localdomain> Content-Type: multipart/mixed; boundary="------------080100010409080306050801" X-SW-Source: 2003-10/txt/msg00844.txt.bz2 This is a multi-part message in MIME format. --------------080100010409080306050801 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-length: 757 > On Oct 27, 6:54pm, Andrew Cagney wrote: > > >> > preferences? >> > >> > At the moment, I prefer the explicit registration of architecture >> > variants. I'd prefer to wait on adding the wildcard mechanism until a >> > more compelling need for it is demonstrated. > >> >> Per the discussion between myself and daniel, the current proposal is to >> add: >> >> > > gdbarch_register_osabi (bfd_arch_powerpc, bfd_mach_ppc, ... >> > > gdbarch_register_osabi (bfd_arch_powerpc, bfd_mach_ppc64, ... >> >> > >> > plus, I believe, either >> > + gdbarch_register_osabi (bfd_arch_rs6000, bfd_mach_rs6k); >> >> to the linux file. Is that pre-approved? > > > Yes. I've checked this in. No more mysterious message during startup! thanks, Andrew --------------080100010409080306050801 Content-Type: text/plain; name="diffs" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="diffs" Content-length: 1167 2003-10-29 Andrew Cagney * ppc-linux-tdep.c (_initialize_ppc_linux_tdep): Instead of the default PPC machine, register 32-bit and 64-bit PPC, and rs6k. Index: ppc-linux-tdep.c =================================================================== RCS file: /cvs/src/src/gdb/ppc-linux-tdep.c,v retrieving revision 1.45 diff -u -r1.45 ppc-linux-tdep.c --- ppc-linux-tdep.c 24 Oct 2003 20:24:06 -0000 1.45 +++ ppc-linux-tdep.c 29 Oct 2003 19:21:33 -0000 @@ -1083,7 +1083,13 @@ void _initialize_ppc_linux_tdep (void) { - gdbarch_register_osabi (bfd_arch_powerpc, 0, GDB_OSABI_LINUX, - ppc_linux_init_abi); + /* Register for all sub-familes of the POWER/PowerPC: 32-bit and + 64-bit PowerPC, and the older rs6k. */ + gdbarch_register_osabi (bfd_arch_powerpc, bfd_mach_ppc, GDB_OSABI_LINUX, + ppc_linux_init_abi); + gdbarch_register_osabi (bfd_arch_powerpc, bfd_mach_ppc64, GDB_OSABI_LINUX, + ppc_linux_init_abi); + gdbarch_register_osabi (bfd_arch_rs6000, bfd_mach_rs6k, GDB_OSABI_LINUX, + ppc_linux_init_abi); add_core_fns (&ppc_linux_regset_core_fns); } --------------080100010409080306050801--