From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9869 invoked by alias); 24 Oct 2003 14:31:16 -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 9862 invoked from network); 24 Oct 2003 14:31:15 -0000 Received: from unknown (HELO localhost.redhat.com) (207.219.125.105) by sources.redhat.com with SMTP; 24 Oct 2003 14:31:15 -0000 Received: from gnu.org (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id CCA0B2B89; Fri, 24 Oct 2003 10:31:11 -0400 (EDT) Message-ID: <3F9937AF.4010201@gnu.org> Date: Fri, 24 Oct 2003 14:31: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: Andrew Cagney Cc: gdb-patches@sources.redhat.com Subject: Re: [patch/rfc,rfa:ppc64] Add osabi wildcard support References: <3F986371.9060708@redhat.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-10/txt/msg00727.txt.bz2 > and the second is to explicitly register both of these architecture variants vis: > > 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); or: + gdbarch_register_osabi (bfd_arch_powerpc, bfd_mach_rs6k); Per this post: http://sources.redhat.com/ml/binutils/2003-10/msg00543.html rs6000:6000 isn't considered compatible with the generic PPC, and hence the OSABI code couldn't find a match. That lead to the warning. Andrew