The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Paul Winalski <paul.winalski@gmail.com>
To: "A. P. Garcia" <a.phillip.garcia@gmail.com>
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] SPARC is CRAPS spelled backwards.
Date: Sun, 23 Sep 2018 17:17:35 -0400	[thread overview]
Message-ID: <CABH=_VR1KrWbN2o7_+RiEOBXmkGsGsKYjMqO4V-TD8Ado+3eTw@mail.gmail.com> (raw)
In-Reply-To: <CAFCBnZufqk1SmOVdWLK19a0oQ1FjFe7ebDDa+T54yrNo=19eDw@mail.gmail.com>

On 9/23/18, A. P. Garcia <a.phillip.garcia@gmail.com> wrote:
>
> In trying to steer this word salad towards some semblance of meaningful
> discussion, is SPARC dead? Practically, yes, I would say so. Or at least it
> seems to be heading in that direction. Is RISC dead? Not at all. ARM is
> doing quite well, and the old "CISC vs RISC" thing seems to be a non-issue
> now, as even the current x86 processors have adopted many design features
> that originated in RISC research.

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.  Modern x86 designs have a
bit of logic stuck in one corner that translates the x86 instruction
stream into a string of RISC-style micro-operations.  The cores
execute the micro-ops.  Micro-op sequences can be cached, so the
translation is done only once for loops.  The result is, as it were,
the best of both worlds--the compactness of a CISC instruction stream
and the simpler and faster circuitry of RISC.

-Paul W.

  reply	other threads:[~2018-09-23 21:18 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 [this message]
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
     [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='CABH=_VR1KrWbN2o7_+RiEOBXmkGsGsKYjMqO4V-TD8Ado+3eTw@mail.gmail.com' \
    --to=paul.winalski@gmail.com \
    --cc=a.phillip.garcia@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).