The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Alexander Voropay <alec@sensi.org>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Design of the AT&T assembly syntax
Date: Tue, 29 Oct 2019 00:48:29 +0300	[thread overview]
Message-ID: <CAGqcPWAdVQU=XAK1QYetrWayAm6ApX=bOjSDDu4DLtM0NdZqbg@mail.gmail.com> (raw)

Robert Clausecker <fuz@fuz.su>wrote:

> The one thing in this chain I have never found is an AT&T style
> assembler for x86 before ELF was introduced.

There were alot of AT&T codebase ports to x86 architecture except Xenix:
Microport, INTERACTIVE, Everex, Wyse e.t.c. using AT&T x86 syntax.

I've tried Microport SystemV /386 (SysV R3.2). It uses COFF
as format for executables:
See:
http://www.vcfed.org/forum/showthread.php?67736-History-behind-the-disk-images-of-AT-amp-T-UNIX-System-V-Release-4-Version-2-1-for-386&p=560039#post560039
(Rather interesting kernel ABI/Call convention)

and
https://gunkies.org/wiki/Unix_SYSVr3

There were also SystemV R2 to i286 ports i.e.:
https://gunkies.org/wiki/Microport_System_V
with a.out binary format.

             reply	other threads:[~2019-10-28 21:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-28 21:48 Alexander Voropay [this message]
2019-10-28 21:59 ` Robert Clausecker
  -- strict thread matches above, loose matches on Subject: below --
2019-10-29 14:38 Alexander Voropay
2019-10-28 20:14 Robert Clausecker
2019-10-28 21:06 ` Seth Morabito
2019-10-29  0:31   ` Nemo Nusquam
2019-10-28 20:07 Robert Clausecker
2019-10-28 22:08 ` Warner Losh
2019-10-28 22:24   ` Robert Clausecker
2019-10-28 22:29     ` Warner Losh

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='CAGqcPWAdVQU=XAK1QYetrWayAm6ApX=bOjSDDu4DLtM0NdZqbg@mail.gmail.com' \
    --to=alec@sensi.org \
    --cc=tuhs@tuhs.org \
    /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 NNTP newsgroup(s).