From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
To: tuhs@minnie.tuhs.org
Cc: jnc@mercury.lcs.mit.edu
Subject: Re: [TUHS] SPARC is CRAPS spelled backwards.
Date: Mon, 24 Sep 2018 07:48:04 -0400 (EDT) [thread overview]
Message-ID: <20180924114804.CFF9B18C082@mercury.lcs.mit.edu> (raw)
> From: Paul Winalski
> In general, a CISC instruction set encoding can express the same
> algorithm more compactly than a RISC instruction set.
I have often pointed to memory bandwidth as one of the key factors in the
evolution of CISC and RISC. When it was low, compared to CPU speeds (most of
the core era), CISC made sense. When it increased (with DRAM), RISC made more
sense, because it allowed CPUs to run faster (via simpler instructions).
Caching made the picture a little more complex; and today, with the incredible
mismatch between memory speeds and CPU speeds, caching dominates, whether you
have RISC or CISC.
Noel
next reply other threads:[~2018-09-24 11:48 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-24 11:48 Noel Chiappa [this message]
-- 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 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 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
[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=20180924114804.CFF9B18C082@mercury.lcs.mit.edu \
--to=jnc@mercury.lcs.mit.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).