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

In short, Ian suggests propigating the patch backwards into the PE
reader, so the internal BFD structures are correct.

1)  I concur completely with the spirit of that.

2) PE is probably better named "not-quite-COFF" but let's not
go there.

3) A fix in the back end propigates itself back to user space
in a way I think Ian should comment upon.  PE basically has
changed the meaning of the s_paddr/lma field, and it's resonable
to have both meanings in the internal data structure in separate
fields.  For most of BFD and its users, that's probably an
improvement, but it presents a problem for objdump.  Either
the format of the --headers output needs to change or there
needs to be special case code so that the "interesting" value
is printed, as a function of the object format being dumped.
(That is, one "COFF" field will go into one of two places; when
printing either both (one guaranteed to be zero) need to be printed,
or objdump needs to know which is "live".)

In general, that problem has been a continuing nuisance about
PE format, so a good solution would probably pay itself back
many times over.

Donn


  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 ` DJ Delorie
1999-07-01  0:00 ` Ian Lance Taylor
1999-07-01  0:00   ` Donn Terry [this message]
1999-07-01  0:00     ` Ian Lance Taylor
  -- strict thread matches above, loose matches on Subject: below --
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=373CF24C.17D32143@verinet.com \
    --to=donn@verinet.com \
    --cc=binutils@sourceware.cygnus.com \
    --cc=ian@airs.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).