From: Chris McGee <newton688@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Is Plan 9 C "Less Dangerous?"
Date: Wed, 5 Sep 2018 07:42:52 -0400 [thread overview]
Message-ID: <CAOk9ws28YMq-UoC98jmFTqe6Qrmcf_0U2Yp6hMDvSjx-un3bDQ@mail.gmail.com> (raw)
In-Reply-To: <CAG2UyHosBfnZz3QD_eR3HFBApsf970VkdYQstWGtc+k5zRcf_g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 625 bytes --]
> Wasn't that the whole point of RISC?
>
It could be, but after having looked briefly at the size of the design for
RISC-V Rocket and especially BOOM I wonder if it's all overly complicated.
They even built their own high level hardware language (Chisel) that
generates Verilog using Scala. Yuck.
Also, there's appears to be quite alot of compiler optimizations in gcc for
RISC-based chips.
Could you get away with a much simpler, smaller hardware design and still
run Plan 9 in a reasonable way? Maybe one side of the software/hardware
divide has to take on more complexity to help simplify the other side?
[-- Attachment #2: Type: text/html, Size: 922 bytes --]
next prev parent reply other threads:[~2018-09-05 11:42 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-02 16:31 Chris McGee
2018-09-02 16:52 ` hiro
2018-09-03 4:07 ` Lucio De Re
2018-09-03 12:40 ` Chris McGee
2018-09-03 17:58 ` Ethan Gardener
2018-09-04 10:51 ` Lucio De Re
2018-09-04 11:33 ` Ethan Gardener
2018-09-04 11:41 ` Chris McGee
2018-09-02 18:16 ` Lucio De Re
2018-09-02 19:18 ` Steve Simon
2018-09-02 19:21 ` Iruatã Souza
2018-09-03 1:03 ` Charles Forsyth
2018-09-03 2:03 ` Skip Tavakkolian
2018-09-04 23:17 ` Charles Forsyth
2018-09-04 23:30 ` Tyga
2018-09-05 2:29 ` Chris McGee
2018-09-05 11:23 ` Dave MacFarlane
2018-09-05 11:42 ` Chris McGee [this message]
2018-09-05 13:35 ` Ethan Gardener
2018-09-05 15:38 ` Iruatã Souza
2018-09-05 23:59 ` Chris McGee
2018-09-06 0:32 ` Bakul Shah
2018-09-06 3:40 ` Lucio De Re
2018-09-06 11:41 ` Chris McGee
2018-09-06 13:37 ` Ethan Gardener
2018-09-06 17:48 ` Richard Miller
2018-09-06 19:08 ` Skip Tavakkolian
2018-09-06 21:21 ` Chris McGee
2018-09-07 8:32 ` Richard Miller
2018-09-05 3:25 ` Ori Bernstein
2018-09-05 8:19 ` Ethan Gardener
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=CAOk9ws28YMq-UoC98jmFTqe6Qrmcf_0U2Yp6hMDvSjx-un3bDQ@mail.gmail.com \
--to=newton688@gmail.com \
--cc=9fans@9fans.net \
/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).