public inbox for gas2@sourceware.org
 help / color / mirror / Atom feed
From: artk@congruent.com (Arthur Kreitman)
To: gnu@cygnus.com
Cc: erich@uruk.org, gas2@cygnus.com, bfd@cygnus.com, gnu@cygnus.com
Subject: traditional Intel & Microsoft formats...
Date: Fri, 11 Nov 1994 05:34:00 -0000	[thread overview]
Message-ID: <9411111311.AA12300@Congruent.COM> (raw)
In-Reply-To: <199411110653.WAA01871@cygnus.com>

>   Specs for some of the formats you are interested in *are* available
>   and don't have to be reverse-engineered.  (Some other info, such as
>   debug sections, may require more work -- I haven't checked into all the
>   details.)  There's an organization of OS and tool companies called the
  As far as what Microsoft is calling their PE format (the one that's being
used for NT and will be used for Windows95, none of those documents you
listed are either complete or valid.

>   Tool Interface Standards committee.  It publishes specs and talks
>   about new formats and revisions.  Cygnus asked how we could join one
>   time, but never got a response.  Here are my old notes about this:
  I think the reason you never got a response it that the effort was
stillborn.  It was announced about the same time as NT was announced.
They advertised that DWARF was the answer to all your problems, and ignored
Microsoft.  They then disappeared.  I don't know if they exist or not,
but I'm certain that Microsoft has continued to enhance aspects of
their object format without asking their permission.


>   By the way, it looks to me like Windows DLL linking is remarkably like
>   dynamic linking on SVR4 or SunOS.  Since the GNU Linker now supports
>   dynamic linking (which was, indeed, a fair bit of work), making it
>   handle DLL's is probably not as big a job as you think.

   I don't think that the mechanism used to support dll's is similar
to sunos shared library support in any way.  Their capabilities
differ significantly.  

>   The way to support any of these formats is to write a new BFD
>   back-end.  It's really pretty easy.  Look at one of the simple ones
  That's the easiest part of supporting the Microsoft formats.  There are
new section types that have to be generated, import tables, export tables,
resources.  BFD get you alot closer, but I would guess that it will
that more resources to get the current BFD to completely support MS
executables then it took to add sunos dynamic linking.

   As an aside, do you know how much work was required to add 
sun dymanic linking.



  parent reply	other threads:[~1994-11-11  5:34 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1994-11-09  8:05 Erich Stefan Boleyn
1994-11-09  8:59 ` Arthur Kreitman
1994-11-09  9:41   ` Erich Stefan Boleyn
1994-11-09  9:56   ` DJ Delorie
1994-11-09  9:57   ` Ken Raeburn
1994-11-09 10:33     ` DJ Delorie
1994-11-09 11:56       ` Erich Stefan Boleyn
1994-11-09 10:49     ` Arthur Kreitman
1994-11-09 12:02       ` Erich Stefan Boleyn
1994-11-10  8:22     ` Richard Stallman
1994-11-10  8:11   ` Richard Stallman
1994-11-10  9:35     ` Erich Stefan Boleyn
1994-11-10 22:53 ` John Gilmore
1994-11-10 23:25   ` John Gilmore
1994-11-11  5:34   ` Arthur Kreitman [this message]
1994-11-11  8:31     ` Ian Lance Taylor
1994-11-11 10:21   ` Erich Stefan Boleyn

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=9411111311.AA12300@Congruent.COM \
    --to=artk@congruent.com \
    --cc=bfd@cygnus.com \
    --cc=erich@uruk.org \
    --cc=gas2@cygnus.com \
    --cc=gnu@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).