From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2976 invoked by alias); 30 Jan 2013 16:44:39 -0000 Received: (qmail 2876 invoked by uid 22791); 30 Jan 2013 16:44:36 -0000 X-SWARE-Spam-Status: No, hits=-3.8 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org Received: from mail-qc0-f170.google.com (HELO mail-qc0-f170.google.com) (209.85.216.170) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 30 Jan 2013 16:44:24 +0000 Received: by mail-qc0-f170.google.com with SMTP id d42so827494qca.15 for ; Wed, 30 Jan 2013 08:44:24 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.224.216.8 with SMTP id hg8mr5685591qab.74.1359564263957; Wed, 30 Jan 2013 08:44:23 -0800 (PST) Received: by 10.49.120.7 with HTTP; Wed, 30 Jan 2013 08:44:23 -0800 (PST) In-Reply-To: <20130130091631.GM3244@bubble.grove.modra.org> References: <20130130091631.GM3244@bubble.grove.modra.org> Date: Wed, 30 Jan 2013 16:44:00 -0000 Message-ID: Subject: Re: [PATCH 1/3] Implement new Linux target vectors on BFD From: "H.J. Lu" To: Sergio Durigan Junior , Binutils Development , GDB Patches , Pedro Alves , Jan Kratochvil , "H. J. Lu" Content-Type: text/plain; charset=ISO-8859-1 X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2013-01/txt/msg00717.txt.bz2 On Wed, Jan 30, 2013 at 1:16 AM, Alan Modra wrote: > On Wed, Jan 30, 2013 at 04:52:46AM -0200, Sergio Durigan Junior wrote: >> 1) Add new target vectors on the BFD configury system in order to handle >> Linux targets, which will then make it possible to use certain functions >> only on such targets, and > > Duplicating targets isn't a really good idea. > > If on my x86_64 linux box I want to build a native binutils that also > supports powerpc64, I can configure binutils with > --enable-targets=powerpc64-linux, or get all targets with > --enable-targets=all. The problem with adding bfd targets as you've > done is that now you have two bfd targets that give equally good > matches for powerpc64 objects. So instead of one "best" match we now > have two. elf64-big will also match, and by a quirk of the way > bfd_check_format_matches operates (giving priority to targets > appearing in config.bfd targ_selvec), this match will be chosen over > the better elf64-powerpc-* matches. That means a worse user > experience for say, "objdump -d". A file that used to happily > disassemble now gives you > > some_file: file format elf64-big > > binutils/objdump: can't disassemble for architecture UNKNOWN! > > You may have noticed that we've already made a mess of targets for > ARM, i386, x86_64 and powerpc. I'd rather not see the same happen for > powerpc64 without a really good reason. > I agree with Alan. I don't want x86 Linux BFD targets. Please find another solution. -- H.J.