public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Fergus Henderson <fjh@cs.mu.OZ.AU>
To: root@jacob.remcomp.fr (root)
Cc: gnu-win32@cygnus.com (gnu-win32)
Subject: Re: Mr Taylor surely understands ld: a correction to my previous post
Date: Thu, 27 Mar 1997 08:16:00 -0000	[thread overview]
Message-ID: <199703270221.NAA05628@mundook.cs.mu.OZ.AU> (raw)
In-Reply-To: <m0w9aec-000AK1C@jacob.remcomp.fr>

Jacob Navia wrote:
> 
> But it is the whole philosophy behind this that is flawed. 
> Mr Taylor writes:
> 
> > ...the linker is able to generate an object file
> > format which is different from the input file formats.  For example,
> > this permits the linker to directly generate S-record output without
> > requiring a convertor.
> 
> But WHY do we have to put the convertor and the linker in the SAME PROGRAM!!!

Here's one possible reason (there may be others).

Different object file formats formats have different sets of capabilities.
In general, conversion from one format to another format may not be
able to preserve all the information.  If the linker required all
inputs to have the same format, then you might have to use a lossy
conversion, and that might prevent successful linking.

One possible solution to this problem would be to invent a new object
file format whose capabilities were a superset of the capabilities of
all other object file formats.  Then, you could ensure that the
conversion to this object file format was non-lossy.  However, this
approach would be more complex than the BFD approach, not less complex.

-- 
Fergus Henderson <fjh@cs.mu.oz.au>   |  "I have always known that the pursuit
WWW: < http://www.cs.mu.oz.au/~fjh >   |  of excellence is a lethal habit"
PGP: finger fjh@128.250.37.3         |     -- the last words of T. S. Garp.
-
For help on using this list, send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

  reply	other threads:[~1997-03-27  8:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-03-25 12:55 Nobody in the world understands Gnu's 'ld' Ian Lance Taylor
1997-03-25 20:52 ` Mr Taylor surely understands ld: a correction to my previous post root
1997-03-27  8:16   ` Fergus Henderson [this message]
1997-03-25 23:17 ` Nobody in the world understands Gnu's 'ld' Fergus Henderson
1997-03-26 10:43   ` Joel Dinolt
1997-03-27  9:46     ` Fergus Henderson
1997-03-27 20:59   ` Pedro A. Aranda Gutiirrez
1997-03-27  9:46     ` Ian Lance Taylor
1997-03-28 10:32       ` Commercial Licensing David Essex
1997-03-28 19:43         ` Jim Balter
1997-03-29  0:06         ` Geoffrey Noer
1997-03-27 22:51   ` Nobody in the world understands Gnu's 'ld' Ian Lance Taylor
1997-03-27  0:57 Mr Taylor surely understands ld: a correction to my previous post Ian Lance Taylor
1997-03-27 15:33 dahms
1997-03-28 10:32 ` Christoph Kukulies

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=199703270221.NAA05628@mundook.cs.mu.OZ.AU \
    --to=fjh@cs.mu.oz.au \
    --cc=gnu-win32@cygnus.com \
    --cc=root@jacob.remcomp.fr \
    /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).