From: cdl@mpl.ucsd.edu (Carl Lowenstein)
Subject: [TUHS] 6-bit, 7-bit and 9-bit byte UNIXes
Date: Thu, 30 Sep 2004 20:59:43 -0700 (PDT) [thread overview]
Message-ID: <200410010359.i913xhf16995@opihi.ucsd.edu> (raw)
> Subject: Re: [TUHS] 6-bit, 7-bit and 9-bit byte UNIXes
> From: Norman Wilson <norman at nose.cs.utoronto.ca>
> To: tuhs at tuhs.org
> Date: Thu, 30 Sep 2004 20:47:22 -0400
>
> The very first UNIX ran on the PDP-7, which had 18-bit words.
>
> I happen to have the assembly-language source code to parts
> of that system. Many programs contain error-handling code
> that does something like this:
>
> lac d1
> sys write; 1f; 1
> jmp somewhere
>
> 1: 077012
>
> ...
>
> d1: 1
>
> Evidently the system thought in words in those days
> (the second argument to sys write is presumably a word
> count), but the single word written is a strong clue
> that 9-bit bytes were used, and that a certain concise
> error message that people love to complain about was
> there from the beginning (and why not?).
?
I would say "the PDP7 computer was word-addressable". In this
context, characters seem to have been packed as 9-bit half-words
in a big-endian fashion. No 'bytes'.
Maybe tomorrow I will be near my DEC literature archives, and see
if I can find some clues about PDP7 instructions that might deal
with half-words. If it's anything like the PDP8 of similar vintage,
there aren't any. Late in its life the PDP8 got a BSW "byte swap"
instruction to swap the half-words in the AC register. 6 bits,
of course.
carl
--
carl lowenstein marine physical lab u.c. san diego
clowenst at ucsd.edu
next reply other threads:[~2004-10-01 3:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-01 3:59 Carl Lowenstein [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-10-01 0:47 Norman Wilson
2004-10-01 1:05 ` Andru Luvisi
2004-09-30 23:46 James Petts
2004-09-30 19:07 Natalia Portillo
2004-09-30 23:57 ` Greg 'groggy' Lehey
2004-10-01 0:21 ` Kenneth Stailey
2004-10-01 0:58 ` Michael Davidson
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=200410010359.i913xhf16995@opihi.ucsd.edu \
--to=cdl@mpl.ucsd.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).