From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1599 invoked by alias); 9 Jan 2002 20:58:08 -0000 Mailing-List: contact binutils-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: binutils-owner@sources.redhat.com Received: (qmail 1374 invoked from network); 9 Jan 2002 20:58:03 -0000 Received: from unknown (HELO cygnus.com) (205.180.230.5) by sources.redhat.com with SMTP; 9 Jan 2002 20:58:03 -0000 Received: from cse.cygnus.com (cse.cygnus.com [205.180.230.236]) by runyon.cygnus.com (8.8.7-cygnus/8.8.7) with ESMTP id MAA16740; Wed, 9 Jan 2002 12:58:00 -0800 (PST) Received: (meissner@localhost) by cse.cygnus.com (8.8.8+Sun/8.6.4) id MAA21671; Wed, 9 Jan 2002 12:57:59 -0800 (PST) Date: Wed, 09 Jan 2002 14:06:00 -0000 From: Michael Meissner To: Hans-Peter Nilsson Cc: binutils@sources.redhat.com Subject: Re: RFC: More stuff in struct bfd_link_info Message-ID: <20020109155759.E20786@cse.cygnus.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from hp@bitrange.com on Tue, Jan 08, 2002 at 09:05:47PM -0500 X-SW-Source: 2002-01/txt/msg00160.txt.bz2 On Tue, Jan 08, 2002 at 09:05:47PM -0500, Hans-Peter Nilsson wrote: > There's a some target-specific cruft in struct bfd_link_info > (for example "int mpc860c0" and "boolean pei386_auto_import") > that could go away (or at least not accumulate) if there was > just a target-specific PTR member, say "PTR target_data". > > Also, I'd like to move "boolean relax" from ld.h:args_type to > struct bfd_link_info, so bfd functions can see whether > relaxation should be done, and perhaps also set it (only) when > necessary; for example if some presumably costly relaxation only > needs to be done if certain relocs are present. > > Thoughts? One historic problem with target-specific PTR members has been when somebody wants to write the program file in another format (S-records, ihex, etc.). These formats don't have the target-specific PTR members. I tend to advise people, link for the standard object file format, and then use objcopy to make a S-record afterwards, instead of telling the linker to make S-records directly. -- Michael Meissner, Red Hat, Inc. (GCC group) PMB 198, 174 Littleton Road #3, Westford, Massachusetts 01886, USA Work: meissner@redhat.com phone: +1 978-486-9304 Non-work: meissner@spectacle-pond.org fax: +1 978-692-4482