From: Paul Winalski <paul.winalski@gmail.com>
To: Norman Wilson <norman@oclsc.org>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: Does anybody know the etymology of the term "word" as in collection of bits?
Date: Fri, 9 Sep 2022 21:35:28 -0400 [thread overview]
Message-ID: <CABH=_VQyDZZRf=faFdJShFUYQYBbwSmU1dGMOvOx4C2KEr3NXA@mail.gmail.com> (raw)
In-Reply-To: <A26778E372C45C9311F9E18B2025E32E.for-standards-violators@oclsc.org>
On 9/9/22, Norman Wilson <norman@oclsc.org> wrote:
>
> IThe DEC-10 had `byte pointers' as well as
> (36-bit) word addresses. A byte pointer comprised an address,
> a starting bit within the addressed word, and a length.
> There were instructions to load and store an addressed byte
> to or from a register, and to do same while incrementing
> the pointer to the next byte, wrapping the start of the next
> word if the remainder of the current word was too small.
> (Bytes couldn't span word boundaries.)
That very closely resembles a field-reference expression in BLISS,
which has the syntax:
addr<start, len, ext> where:
addr is an expression whose value is the address of the BLISS word
containing the field
start is an expression whose value is the stating offset within that
word of the field
len is an expression giving the length of the field in bits
ext is an expression whose value is either 0 0r 1 that tells how to
pad out the field to a full BLISS word size
It's probably no accident that BLISS field expressions match this
feature of the DEC-10 hardware.
-Paul W.
next prev parent reply other threads:[~2022-09-10 1:36 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-09 18:46 Norman Wilson
2022-09-10 1:35 ` Paul Winalski [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-09-11 13:30 Douglas McIlroy
2022-09-11 15:08 ` John Cowan
2022-09-11 15:30 ` Bakul Shah
2022-09-11 15:45 ` Paul Winalski
2022-09-11 16:20 ` Steve Nickolas
2022-09-09 19:39 Nelson H. F. Beebe
2022-09-09 20:27 ` Bakul Shah
2022-09-09 21:12 ` Henry Bent
2022-09-09 21:44 ` Dave Horsfall
2022-09-09 17:26 Douglas McIlroy
2022-09-09 1:33 Douglas McIlroy
2022-09-09 2:12 ` Larry McVoy
2022-09-13 14:23 ` John Foust via TUHS
2022-09-09 2:45 ` George Michaelson
2022-09-16 5:55 ` Marc Donner
2022-09-08 21:16 Noel Chiappa
2022-09-08 21:24 ` Dan Halbert
2022-09-08 18:20 Noel Chiappa
2022-09-08 19:28 ` Jim Capp
2022-09-08 16:51 [TUHS] " Jon Steinhart
2022-09-08 16:56 ` [TUHS] " Andrew Hume
2022-09-08 17:28 ` Dan Halbert
2022-09-09 0:00 ` Greg 'groggy' Lehey
2022-09-09 15:49 ` Paul Winalski
2022-09-09 18:44 ` Bakul Shah
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=_VQyDZZRf=faFdJShFUYQYBbwSmU1dGMOvOx4C2KEr3NXA@mail.gmail.com' \
--to=paul.winalski@gmail.com \
--cc=norman@oclsc.org \
--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).