From: Aron Insinga <aki@insinga.com>
To: coff@tuhs.org
Subject: [COFF] Re: machine code translation,as mental architecture models
Date: Fri, 12 Jul 2024 20:25:56 -0400 [thread overview]
Message-ID: <e9c04527-a019-4b05-8160-ab483d402776@insinga.com> (raw)
In-Reply-To: <20240712220328.C332A8F7A3EF@ary.qy>
I think my work was in the summer of 1979 or possibly 1980, before the
FRS in Oct. 1980. People were happy because mass production of the
ucode ROMs hadn't started yet. I was using one of the 2~4 11/750
prototypes which were on concrete blocks in a lab, and the 11/730
breadboard was standing up on a table (no box) with its boards fanned
out. And it was during the gasoline shortage. Maybe I'll find
something about it later.
- Aron
On 7/12/24 18:03, John Levine wrote:
> It appears that Dave Horsfall <dave@horsfall.org> said:
>> On Sat, 12 Jul 2024, John R Levine wrote:
>>
>>> Our Vaxes ran Unix so it was all C other than a few things like tracking
>>> down a bug in the 11/750's microcode that broke an instruction in the
>>> inner loop of printf(). [...]
>> Do tell...
> The details are a litle dim after 45 years, but there was a MOVTUC
> instruction in the inner loop of printf that scanned for the null at
> the end of the string. The /750 had a microcode bug that didn't
> matter for the way DEC's software used it but broke the libc and
> I think also the kernel version. MOVTUC sets six registers and
> we probably used one they didn't.
>
> Bill replaced it with a few simpler instructions and the comment
>
> ; Comet sucks
>
> R's,
> John
>
> PS: For you young folks, Comet was DEC's internal project name for the /750.
next prev parent reply other threads:[~2024-07-13 0:26 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAEoi9W4Nr8DyvgVKXZ+5ZQJEayFpMw=mLW_0STtZaATSZcCFYg@mail.gmail.com>
[not found] ` <20240710203422.284BA18C077@mercury.lcs.mit.edu>
[not found] ` <011a1e2a-6a73-ceaa-2b9c-9ca43daf41e7@bitsavers.org>
[not found] ` <20240710230010.D2D968F5DEE4@ary.qy>
2024-07-10 23:14 ` [COFF] Re: [TUHS] " segaloco via COFF
[not found] ` <20240710212641.E24548F5C32C@ary.qy>
2024-07-11 1:29 ` 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-11 20:32 ` Dave Horsfall
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 [this message]
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-12 16:54 ` [COFF] Re: [TUHS] Re: history of machine code translation,as " John R Levine
[not found] ` <CAEoi9W4tNyEUcHytGFOCQRGS8C+FMWcKU3Wa3YuxVsC+4-24vw@mail.gmail.com>
[not found] ` <a85b24bb-b024-b5fe-1fc8-a8e18f732a8d@taugh.com>
2024-07-13 19:51 ` Dan Cross
2024-07-13 11:09 [COFF] " Douglas McIlroy
2024-07-13 17:36 ` Paul Winalski
2024-07-13 21:05 ` Aron Insinga
2024-07-14 15:55 ` Paul Winalski
2024-07-14 17:29 ` G. Branden Robinson
2024-07-13 22:00 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=e9c04527-a019-4b05-8160-ab483d402776@insinga.com \
--to=aki@insinga.com \
--cc=coff@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).