From: Lars Brinkhoff via TUHS <tuhs@tuhs.org>
To: Phillip Harbison via TUHS <tuhs@tuhs.org>
Cc: Phillip Harbison <alvitar@xavax.com>
Subject: [TUHS] Re: [COFF] SOSP 1973 [was Multics<->Unix Re: Re: History of cal(1)?
Date: Mon, 22 Sep 2025 15:41:14 +0000 [thread overview]
Message-ID: <7wwm5qebqd.fsf@junk.nocrew.org> (raw)
In-Reply-To: <a4c3ef33-3212-44a4-a16a-9c8d79dbaeb0@xavax.com> (Phillip Harbison via TUHS's message of "Mon, 22 Sep 2025 10:19:19 -0500")
Phillip Harbison wrote:
> UNIVAC 1100 says hi.
> - 36-bit general purpose A(ccumulator) registers.
> - 36-bit and 72-bit floating point
> - indeX registers split into 18-bit address (because who would ever
> need to address more than 256K words?) and 18-bit auto-increment
> - 6-bit characters (Fieldata). ASCII support added later with 9-bit
> characters (not sure how they used thew extra bit)
> - octal preferred here ;)
And for yet more fun, one's complement. After having worked on a PDP-10
backend for GCC, I looked into this one. But it never went anywhere.
next prev parent reply other threads:[~2025-09-22 15:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-19 21:49 [TUHS] Re: [COFF] SOSP 1973 [was Multics<->Unix Re: Re: History of cal(1)? Noel Chiappa via TUHS
2025-09-19 21:59 ` Charles H Sauer (he/him) via TUHS
2025-09-21 1:12 ` John Levine via TUHS
2025-09-21 5:25 ` Niklas Karlsson via TUHS
2025-09-22 12:51 ` Lars Brinkhoff via TUHS
2025-09-22 15:19 ` Phillip Harbison via TUHS
2025-09-22 15:24 ` Phillip Harbison via TUHS
2025-09-22 15:41 ` Lars Brinkhoff via TUHS [this message]
2025-09-22 16:45 ` Phillip Harbison via TUHS
2025-09-24 0:33 ` Dave Horsfall via TUHS
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=7wwm5qebqd.fsf@junk.nocrew.org \
--to=tuhs@tuhs.org \
--cc=alvitar@xavax.com \
--cc=lars@nocrew.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).