public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <ian@airs.com>
To: nickc@cygnus.com
Cc: binutils@sourceware.cygnus.com
Subject: Re: Proposed objcopy patch
Date: Thu, 01 Jul 1999 00:00:00 -0000	[thread overview]
Message-ID: <19990515011618.765.qmail@daffy.airs.com> (raw)
In-Reply-To: <199905142116.OAA18159@elmo.cygnus.com>

   Date: Fri, 14 May 1999 14:16:02 -0700
   From: Nick Clifton <nickc@cygnus.com>

     Would anyone care to comment on the patch below ?  It is a nasty hack
     which fixes a problem encountered when using objcopy to convert from
     a PE format image file into SRECs.  The PE format uses the LMA field
     as a virtual size rather a physical address, which confuses BFD when
     it comes to try to generate SRECs.

Please, no.  The LMA in isection->lma is in a BFD internal structure.
Those structures should be storing generic information.  That is, the
LMA field should always hold the LMA.  If the section lma field does
not hold the LMA for PE, then the correct solution is to change the PE
backend to store the correct value in the section lma field.  Right
now PE is probably simply setting the LMA field from the s_paddr
field; that would have to change.

Of course, the PE backend may rely on this on other ways, so the true
section size would to be stored elsewhere in PE specific information,
and any code which expected to see the section size in the lma field
would have to be changed.

Basically, though, it's unacceptable to change objcopy in order to
support a specific file format.  That destroys the whole point of
using BFD in the first place.

Ian

  reply	other threads:[~1999-07-01  0:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-01  0:00 Nick Clifton
1999-07-01  0:00 ` Ian Lance Taylor [this message]
1999-07-01  0:00   ` Donn Terry
1999-07-01  0:00     ` Ian Lance Taylor
1999-07-01  0:00 ` DJ Delorie
1999-07-01  0:00 Nick Clifton
1999-07-01  0:00 Nick Clifton

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=19990515011618.765.qmail@daffy.airs.com \
    --to=ian@airs.com \
    --cc=binutils@sourceware.cygnus.com \
    --cc=nickc@cygnus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).