From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31923 invoked by alias); 14 May 2002 08:50:17 -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 31876 invoked from network); 14 May 2002 08:50:14 -0000 Received: from unknown (HELO dell-pe2450-3.cambridge.redhat.com) (195.224.55.225) by sources.redhat.com with SMTP; 14 May 2002 08:50:14 -0000 Received: from north-pole.nickc.cambridge.redhat.com (host217-39-2-165.in-addr.btopenworld.com [217.39.2.165]) by dell-pe2450-3.cambridge.redhat.com (Postfix) with ESMTP id 3E7DC84B98; Tue, 14 May 2002 09:50:13 +0100 (BST) Received: from north-pole.nickc.cambridge.redhat.com.nickc.cambridge.redhat.com (localhost [127.0.0.1]) by north-pole.nickc.cambridge.redhat.com (Postfix) with ESMTP id 969611C39B; Tue, 14 May 2002 09:50:03 +0100 (BST) To: Elena Zannoni Cc: thorpej@wasabisystems.com, binutils@sources.redhat.com, gdb-patches@sources.redhat.com Subject: Re: [PATCH/RFA] Include sh64 support for shle-*-netbsdelf* References: <20020511115603.W3435@dr-evil.shagadelic.org> <20020513082324.R3435@dr-evil.shagadelic.org> <15584.11203.728429.774659@localhost.redhat.com> From: Nick Clifton Date: Tue, 14 May 2002 01:50:00 -0000 In-Reply-To: <15584.11203.728429.774659@localhost.redhat.com> Message-ID: User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2002-05/txt/msg00532.txt.bz2 Hi Elena, > > + shle-*-netbsdelf*) > > + targ_defvec=bfd_elf32_shlnbsd_vec > > + targ_selvecs="bfd_elf32_shnbsd_vec shcoff_vec shlcoff_vec" > > +#ifdef BFD64 > > + targ_selvecs="${targ_selvecs} bfd_elf32_sh64_vec bfd_elf32_sh64l_vec bfd_elf64_sh64_vec bfd_elf64_sh64l_vec" > > +#endif > > + ;; > > sh*le-*-netbsdelf*) > > targ_defvec=bfd_elf32_shlnbsd_vec > > targ_selvecs="bfd_elf32_shnbsd_vec shcoff_vec shlcoff_vec" > Wouldn't the same change be required to build sh*le-*-netbdself* ? Err, no. I think that Jason's point was that support for the SH64 architecture was only desireable if the configure target was "sh" and not "sh3" or "sh4". Presumably "sh" is intended to mean "any SH processor" whereas "sh3" means "only the SH3 processor". > The tdep gdb file is going to be built for all the sh targets. And > that file requires the sh64 disassembly functions. In which case there may well be a problem. As it stands configuring BFD as, eg, sh3-elf will not bring in the sh64 architecture or disassembly functions. Can the tdep file be made conditional on the SH architecture specified on the configure command line ? Cheers Nick