9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Skip Tavakkolian <skip.tavakkolian@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: Thu,  6 Sep 2018 12:08:55 -0700	[thread overview]
Message-ID: <CAJSxfmJnYUbTpP6=CbY16ZY_zbbe1iykezkwsX981tHqv+dPFQ@mail.gmail.com> (raw)
In-Reply-To: <CADq+LhP7KPins4YsHKeCr+3ikFc9tQmYtj7i60V-zqR8M=J00w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1500 bytes --]

Thank you.  This is fantastic.

I've been looking into running Plan 9 in JSLinux (
https://bellard.org/jslinux/  and https://bellard.org/jslinux/tech.html)
and came across riscvemu (https://bellard.org/riscvemu/). I wonder if it
might be a useful for trying things on.

On Thu, Sep 6, 2018 at 10:48 AM Richard Miller <9fans@hamnavoe.com> wrote:

> > 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.
>
> It's possible to build a simple and perfectly usable RISC-V processor
> on an FPGA in verilog.  The one I use is
> https://github.com/cliffordwolf/picorv32 , written by Clifford Wolf.
> Its small size means it can be (and has been) formally verified, and
> (for some applications at least) you can compensate for the modest
> performance by putting lots of them on one chip.
>
> > Also, there's appears to be quite alot of compiler optimizations in gcc
> for
> > RISC-based chips.
>
> Again, it's possible to build a simple and perfectly usable C compiler
> for RISC-V without going overboard with optimisation.  I've been
> working on re-targeting the Plan 9 C toolchain for RISC-V.  It's at
> the stage where it can successfully compile itself, but floating point
> support is not yet complete.  If anyone is interested, let me know.
>
>

[-- Attachment #2: Type: text/html, Size: 2106 bytes --]

  reply	other threads:[~2018-09-06 19:08 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
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 [this message]
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='CAJSxfmJnYUbTpP6=CbY16ZY_zbbe1iykezkwsX981tHqv+dPFQ@mail.gmail.com' \
    --to=skip.tavakkolian@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).