The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Tony Finch <dot@dotat.at>
To: Paul Winalski <paul.winalski@gmail.com>
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] SPARC is CRAPS spelled backwards.
Date: Mon, 24 Sep 2018 12:25:46 +0100	[thread overview]
Message-ID: <alpine.DEB.2.20.1809241212560.3596@grey.csi.cam.ac.uk> (raw)
In-Reply-To: <CABH=_VR1KrWbN2o7_+RiEOBXmkGsGsKYjMqO4V-TD8Ado+3eTw@mail.gmail.com>

Paul Winalski <paul.winalski@gmail.com> wrote:
>
> In general, a CISC instruction set encoding can express the same
> algorithm more compactly than a RISC instruction set.  Once CISC
> technology solved the instruction pipelining and decoding problem, it
> gained an advantage over RISC architectures such as Alpha because the
> instruction set stream was less verbose.

It's more subtle than that, I think. One of the best contributions to this
discussion was John Mashey's classic comp.arch article (which I originally
read in 1994, I think) -

https://yarchive.net/comp/risc_definition.html

What is striking about it is that the two dominant architectures now are
(very roughly) the least CISCy CISC and the least RISCy RISC. In
particular x86 did not go in for elaborate addressing modes and highly
orthogonal instruction sets that allow you to use the elaborate addressing
modes multiple times in one instruction. (Compare it with later 68Ks, for
contrast.) So the translation to RISC-style micro-ops does not end up with
ridiculously long dependency chains within most instructions.

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
Shannon: South 3 or 4, increasing 5 to 7, perhaps gale 8 later. Moderate,
becoming rough, then very rough later in far northwest. Fair then occasional
rain. Good, becoming moderate, occasionally poor.

  reply	other threads:[~2018-09-24 11:26 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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 [this message]
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
     [not found]                 ` <ceae72ff-ca8b-4cc1-9666-82253c1e1683.maildroid@localhost>
2018-09-26 16:02                   ` [TUHS] Fwd: " William Pechter
2018-09-26 18:24                 ` [TUHS] " 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
2018-09-24 11:48 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-25 18:41 Noel Chiappa
2018-09-27  7:35 Paul Ruizendaal
2018-09-27  7:52 ` Arrigo Triulzi
2018-09-27 18:03 Nelson H. F. Beebe
2018-09-27 19:34 ` Nemo
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
2018-09-27 21:07 Norman Wilson
2018-09-28 12:08 Nelson H. F. Beebe

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.DEB.2.20.1809241212560.3596@grey.csi.cam.ac.uk \
    --to=dot@dotat.at \
    --cc=paul.winalski@gmail.com \
    --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).