From: Warner Losh <imp@bsdimp.com>
To: Robert Clausecker <fuz@fuz.su>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Design of the AT&T assembly syntax
Date: Mon, 28 Oct 2019 16:29:26 -0600 [thread overview]
Message-ID: <CANCZdfooqSDFTPouDgmOGFWqzEOpFrJ8oGRAHS8k_+VZDsboGQ@mail.gmail.com> (raw)
In-Reply-To: <20191028222417.GA45136@fuz.su>
[-- Attachment #1: Type: text/plain, Size: 1195 bytes --]
On Mon, Oct 28, 2019 at 4:24 PM Robert Clausecker <fuz@fuz.su> wrote:
> Hi Warner,
>
> On Mon, Oct 28, 2019 at 04:08:53PM -0600, Warner Losh wrote:
> > VENIX 2.0 had this. It was a Pure AT&T syntax w/o % signs:
> >
> > eg
> > |
> > | VENIX/86 start off (bootstrap starts execution at location 0 `start').
> > |
> > | Relocate complete kernel down to low memory.
> > .text
> > start: cli
> > mov dx,#LOWMEM | base of relocated kernel
> > mov cx,cs
> > cmp cx,dx | are we there (put there by bootstrap) ?
> > beq L0002 | Yes.
> > mov ds,cx
> >
> > which is clearly op dst, src.
>
> op dst, src is Intel syntax. AT&T syntax has op src, dst like MACRO-11.
> There are a number of other differences: (a) | instead of / or # as a
> comment
> character (b) different mnemonics (beq instead of je) and (c) # instead of
> $
> as the comment character.
>
> Without seeing some more code, I'd say it's not AT&T syntax.
>
Doh! I've been mixing the two up since the 90s :(. Yea, this stuff isn't
AT&T syntax... It's from a compiler from MIT... I should have taken the
hint that it used MIT sequence :)
Warner
[-- Attachment #2: Type: text/html, Size: 1766 bytes --]
next prev parent reply other threads:[~2019-10-28 22:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2019-10-28 20:14 Robert Clausecker
2019-10-28 21:06 ` Seth Morabito
2019-10-29 0:31 ` Nemo Nusquam
2019-10-28 21:48 Alexander Voropay
2019-10-28 21:59 ` Robert Clausecker
2019-10-29 14:38 Alexander Voropay
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=CANCZdfooqSDFTPouDgmOGFWqzEOpFrJ8oGRAHS8k_+VZDsboGQ@mail.gmail.com \
--to=imp@bsdimp.com \
--cc=fuz@fuz.su \
--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).