The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Nemo <cym224@gmail.com>
To: "Nelson H. F. Beebe" <beebe@math.utah.edu>
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] SPARC is CRAPS spelled backwards.
Date: Thu, 27 Sep 2018 15:34:38 -0400	[thread overview]
Message-ID: <CAJfiPzzNudEP3KZ+pUmP__8qW9Dnx7QTt488GWvEG5A2OU0Fhw@mail.gmail.com> (raw)
In-Reply-To: <CMM.0.95.0.1538071406.beebe@gamma.math.utah.edu>

On 27/09/2018, Nelson H. F. Beebe <beebe@math.utah.edu> wrote:
> As a followup to discussions on this thread about hardware
> architectures, some of you may be interested in this new letter
> published today:
>
> 	Letters to the editor: Hennessy and Patterson on the roots of RISC
> 	Comm. ACM 61(10) 6 (2018)
> 	https://doi.org/10.1145/3273019
> 	http://delivery.acm.org/10.1145/3280000/3273019/p6-friedman.pdf

Also of interest may be the video "SPARC at 25"
(https://www.youtube.com/watch?v=w3ukXhEaYGI ), wherein Patterson,
Joy, and others discuss SPARC.  (Joy's comment on register windows is
interesting and matches Brooks' remark.)

N.

>
> The short two-paragraph letter is from Fred Brooks, noted computer
> architect, author, and computer scientist.
>
> -------------------------------------------------------------------------------
> - Nelson H. F. Beebe                    Tel: +1 801 581 5254
>  -
> - University of Utah                    FAX: +1 801 581 4148
>  -
> - Department of Mathematics, 110 LCB    Internet e-mail: beebe@math.utah.edu
>  -
> - 155 S 1400 E RM 233                       beebe@acm.org
> beebe@computer.org -
> - Salt Lake City, UT 84112-0090, USA    URL:
> http://www.math.utah.edu/~beebe/ -
> -------------------------------------------------------------------------------
>

  reply	other threads:[~2018-09-27 19:35 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-27 18:03 Nelson H. F. Beebe
2018-09-27 19:34 ` Nemo [this message]
2018-09-27 20:30 ` Dan Cross
2018-09-27 20:51   ` Cág
2018-09-27 21:01     ` Henry Bent
2018-09-27 21:04       ` Cág
  -- strict thread matches above, loose matches on Subject: below --
2018-09-28 12:08 Nelson H. F. Beebe
2018-09-27 21:07 Norman Wilson
2018-09-27  7:35 Paul Ruizendaal
2018-09-27  7:52 ` Arrigo Triulzi
2018-09-25 18:41 Noel Chiappa
2018-09-25 12:12 Noel Chiappa
2018-09-25 14:49 ` Theodore Y. Ts'o
2018-09-26 19:31   ` Derek Fawcus
2018-09-25 15:29 ` Arthur Krewat
2018-09-24 11:48 Noel Chiappa
     [not found] <mailman.98.1535822297.3725.tuhs@minnie.tuhs.org>
2018-09-23 18:37 ` Don Hopkins
2018-09-23 19:49   ` A. P. Garcia
2018-09-23 21:17     ` Paul Winalski
2018-09-24 11:25       ` Tony Finch
2018-09-24 19:46       ` Peter Jeremy
2018-09-24 20:20         ` Paul Winalski
2018-09-24 20:45           ` Arthur Krewat
2018-09-26  6:20             ` Peter Jeremy
2018-09-26  6:46               ` Lars Brinkhoff
2018-09-26 15:03                 ` Theodore Y. Ts'o
2018-09-26 15:32                   ` Paul Winalski
2018-09-26 15:44               ` Henry Bent
2018-09-26 18:24                 ` Donald ODona
2018-09-25 10:00         ` Tony Finch
2018-09-25 15:01           ` Larry McVoy
2018-09-25 19:48             ` Peter Jeremy
2018-09-25 18:34           ` Paul Winalski

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=CAJfiPzzNudEP3KZ+pUmP__8qW9Dnx7QTt488GWvEG5A2OU0Fhw@mail.gmail.com \
    --to=cym224@gmail.com \
    --cc=beebe@math.utah.edu \
    --cc=tuhs@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).