From: Paul Winalski <paul.winalski@gmail.com>
To: Douglas McIlroy <douglas.mcilroy@dartmouth.edu>
Cc: COFF <coff@tuhs.org>
Subject: [COFF] Re: machine code translation,as mental architecture models
Date: Sat, 13 Jul 2024 13:36:20 -0400 [thread overview]
Message-ID: <CABH=_VS_D69G3=6YiCS2eyrkcCXYQ4nJ=OZ3zhUh-vKX3q6prQ@mail.gmail.com> (raw)
In-Reply-To: <CAKH6PiWXBTqEP7y0X3ArW2vctj350buc8P9StHuBW8+2tfzwRg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 915 bytes --]
On Sat, Jul 13, 2024 at 9:35 AM Douglas McIlroy <
douglas.mcilroy@dartmouth.edu> wrote:
> > Well, doesn't it depend on whether VAX MACRO kept the macros as
> > high-level entities when translating them, or if it processed macros in
> > the familiar way into instructions that sat at the same level as
> > hand-written ‘assembler’. I don't think this thread has made that clear
> > so far.
>
> The VAX MACRO compiler treats macros the same way that the assembler
treats them. It expands them into individual assembler statements (i.e.,
instructions, labels, data definitions, etc.). VAX MACRO then translates
those into compiler intermediate language (originally GEM EIL [expanded
intermediate language], nowadays probably LLVM IL).
Neither the VAX assembler nor the VAX MACRO compiler treats macros as
high-level entities. I know of no assembler that would do such a thing.
-Paul W.
[-- Attachment #2: Type: text/html, Size: 1316 bytes --]
next prev parent reply other threads:[~2024-07-13 17:36 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-13 11:09 Douglas McIlroy
2024-07-13 17:36 ` Paul Winalski [this message]
2024-07-13 21:05 ` Aron Insinga
2024-07-14 15:55 ` Paul Winalski
2024-07-14 17:29 ` G. Branden Robinson
[not found] <20240710203422.284BA18C077@mercury.lcs.mit.edu>
[not found] ` <20240710212641.E24548F5C32C@ary.qy>
2024-07-11 1:29 ` [COFF] Re: [TUHS] " Dan Cross
[not found] ` <18977302-8934-ec96-9154-b3c53824e506@taugh.com>
2024-07-11 2:05 ` Dan Cross
2024-07-11 16:50 ` Paul Winalski
2024-07-12 16:23 ` John R Levine
2024-07-12 16:51 ` [COFF] " Paul Winalski
2024-07-12 17:02 ` John R Levine
2024-07-12 20:52 ` Dave Horsfall
2024-07-12 22:03 ` John Levine
2024-07-13 0:25 ` Aron Insinga
2024-07-13 0:27 ` Dave Horsfall
2024-07-13 1:19 ` Paul Winalski
[not found] ` <CABH=_VS8z6ayJSQab0u5Cxw--hM8px8-eFGjeFCKTXxe <alpine.BSF.2.21.9999.2407131018370.6233@aneurin.horsfall.org>
2024-07-13 2:25 ` John Levine
2024-07-13 9:57 ` [COFF] Re: machine code translation, as " Ralph Corderoy
2024-07-13 14:25 ` Dan Cross
2024-07-13 17:27 ` Aron Insinga
2024-07-12 17:03 ` [COFF] Re: machine code translation,as " Stuff Received
2024-07-12 18:01 ` Paul Winalski
2024-07-12 20:35 ` John Levine
2024-07-13 9:26 ` [COFF] Re: machine code translation, as " Ralph Corderoy
2024-07-12 18:54 ` [COFF] Re: machine code translation,as " Aron Insinga
2024-07-12 21:49 ` Dave Horsfall
[not found] ` <20240710203422.284BA18C077@mercury.lcs. <20240713095708.203D5220C9@orac.inputplus.co.uk>
2024-07-13 18:50 ` [COFF] Re: machine code translation, as " John Levine
2024-07-13 19:27 ` Paul Winalski
2024-07-13 19:42 ` Dan Cross
2024-07-14 1:09 ` Aron Insinga
2024-07-14 1:46 ` Aron Insinga
2024-07-14 16:16 ` Paul Winalski
2024-07-13 22:00 [COFF] Re: machine code translation,as " Douglas McIlroy
2024-07-13 23:46 ` John Levine
2024-07-14 0:54 ` Dan Cross
2024-07-14 1:04 ` Aron Insinga
2024-07-14 0:56 ` Aron Insinga
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='CABH=_VS_D69G3=6YiCS2eyrkcCXYQ4nJ=OZ3zhUh-vKX3q6prQ@mail.gmail.com' \
--to=paul.winalski@gmail.com \
--cc=coff@tuhs.org \
--cc=douglas.mcilroy@dartmouth.edu \
/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).