From: Robert Clausecker <fuz@fuz.su>
To: Alexander Voropay <alec@sensi.org>
Cc: tuhs@tuhs.org
Subject: Re: [TUHS] Design of the AT&T assembly syntax
Date: Mon, 28 Oct 2019 22:59:16 +0100 [thread overview]
Message-ID: <20191028215916.GA43520@fuz.su> (raw)
In-Reply-To: <CAGqcPWAdVQU=XAK1QYetrWayAm6ApX=bOjSDDu4DLtM0NdZqbg@mail.gmail.com>
Hi Alexander,
On Tue, Oct 29, 2019 at 12:48:29AM +0300, Alexander Voropay wrote:
> 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)
Nice find! It seems to use lcall to selector 7 for system calls. A
similar choice was made in 386BSD all the way through FreeBSD 2.2.8
where it was replaced with int $0x80 as in Linux.
> 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.
I'll have a look at that.
Thank you for the help!
Yours,
Robert Clausecker
--
() ascii ribbon campaign - for an 8-bit clean world
/\ - against html email - against proprietary attachments
next prev parent reply other threads:[~2019-10-28 21:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-28 21:48 Alexander Voropay
2019-10-28 21:59 ` Robert Clausecker [this message]
-- 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=20191028215916.GA43520@fuz.su \
--to=fuz@fuz.su \
--cc=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).