public inbox for gas2@sourceware.org
 help / color / mirror / Atom feed
From: Erich Stefan Boleyn <erich@uruk.org>
To: gas2@cygnus.com, bfd@cygnus.com
Subject: traditional Intel & Microsoft formats...
Date: Wed, 09 Nov 1994 08:05:00 -0000	[thread overview]
Message-ID: <199411091607.IAA20118@uruk.org> (raw)

Greetings.

I'm curious if there is an intention of any on these lists to
try to be able to (for the i386 processor series):

  1) assemble (GAS) and manipulate (BFD) traditional Intel/Microsoft
     16-bit code (OMF/NE formats).

  2) assemble (GAS) and manipulate (BFD) traditional Intel/Microsoft
     32-bit code (OMF/PE formats).

"assemble" is reasonably obvious, but by "manipulate", I mean support
in the full sense of the BFD library code, so that you could (if
possible) link it via the GNU linker with other object file formats,
etc.

My interest is mostly as targets, not as hosts, and the 16-bit assembly
is less interesting to me (though I saw the message posted about
others being interested in 16-bit assembly).

The goal behind this is that, well, I'd already announced on the
BFD list working on a BFD-based dynamic linker...  well, my long-term
goal would be a flexible binary emulation system using the
BFD to handle format and system-dependent structures and symbols.

The idea would be that the HURD (and Linux, FreeBSD, too if others cared
to port it, though it is easier on the HURD, I think) could then run
MS-Windows 3.1, DOS, NT, and Chicago applications regardless of the
host processor, and at native speeds if you have a processor
with an "Intel 386 emulation mode" in hardware.

Well, all that is far off, but some essential parts are the items
mentioned above.

The BFD already supports the object file formats of other UNIX-like
OS's, so that's mostly work on the side of the emulator piece.

Anyway, I'm tossing this out for those who might be interested/
are thinking about working on such support/might be now...

Thanks for your time.

Erich Boleyn
--
Erich Stefan Boleyn               \__   E-mail (preferred):  <erich@uruk.org>
Mathematician, Software Engineer     \__   home #:   +1 (503) 226-0741
Mad Genius wanna-be, CyberMuffin        \_ phys loc: 924 S.W. 16th Ave, #202
Motto: "I'll live forever or die trying"  \          Portland, OR, USA  97205


             reply	other threads:[~1994-11-09  8:05 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1994-11-09  8:05 Erich Stefan Boleyn [this message]
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
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=199411091607.IAA20118@uruk.org \
    --to=erich@uruk.org \
    --cc=bfd@cygnus.com \
    --cc=gas2@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).