Computer Old Farts Forum
 help / color / mirror / Atom feed
From: dave at horsfall.org (Dave Horsfall)
Subject: [COFF] In memoriam: Gene Amdahl
Date: Tue, 12 Nov 2019 08:38:02 +1100 (EST)	[thread overview]
Message-ID: <alpine.BSF.2.21.9999.1911120832450.11612@aneurin.horsfall.org> (raw)
In-Reply-To: <CAC20D2NqS2D-GPqbmb1bzhOOkV5zM3e-eZ-9a1Gi76hktwRO7Q@mail.gmail.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1029 bytes --]

On Mon, 11 Nov 2019, Clem Cole wrote:

> According to my friend Russ Robulen (his coworker, lead on the 360/50, 
> worked on /91 and later lead for the IBM ASC),  Amdahl wanted the byte 
> to be 7-bits for S/360, but Fred Brook's overruled him.  Brooks was said 
> to have thrown Amdahl out his office and told him "not come back unless 
> it was a power of 2", as "he could not program it sanely otherwise."  
>  Amdahl semi-won the 24/32 bit war.   Brooks let he have a 24 bit basic 
> word, only if it stored it as 32 bits and ensured that all pointers were 
> stored in the same.  Russ says that Amdahl always thought both choices 
> were a terrible waste of hardware.   Gordon Bell later said, those two 
> choices were the most important in S/360's lasting impact.

Interesting; I'll try and summarise that for my calendar.  In the meantime 
I'm glad that Brooks' view prevailed, having worked with byte-less 12-bit 
(PDP-8) and 60-bit (CDC); I don't remember the word length of the 
Burroughs series.

-- Dave


  reply	other threads:[~2019-11-11 21:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-09 22:09 dave
2019-11-11 15:05 ` clemc
2019-11-11 21:38   ` dave [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-11-10  0:18 dave

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=alpine.BSF.2.21.9999.1911120832450.11612@aneurin.horsfall.org \
    --to=coff@minnie.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).