caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Richard W.M. Jones" <rich@annexia.org>
To: caml-list@inria.fr, "Nicolás Ojeda Bär" <nicolas.ojeda.bar@lexifi.com>
Subject: [Caml-list] Status of the OCaml RISC-V port
Date: Sun, 25 Feb 2018 16:14:30 +0000	[thread overview]
Message-ID: <20180225161430.zkfpkihg7jyxs5cg@annexia.org> (raw)


Fedora has been maintaining an out of tree RISC-V patch in our OCaml
package for about 18 months, from:

  https://github.com/nojb/riscv-ocaml/commits/trunk

This has proven to be fairly stable, and I'm wondering when / under
what conditions it can go upstream?

RISC-V finally settled on a stable libc ABI (contributed to glibc
2.27) which has allowed us to start porting Fedora to RISC-V for real.
You can grab bootable disk images from:

  https://fedorapeople.org/groups/risc-v/disk-images/

and inside run 'dnf install ocaml' which will currently install
OCaml 4.06.0 with native RISC-V support.  There is also sshd,
systemd, gcc, etc., albeit lacking emacs :-(

At the moment you can run these on an out of tree qemu patch:

  https://github.com/riscv/riscv-qemu/tree/qemu-upstream-v6

which supports multiple virtual CPUs and (if you have fast enough
hardware) is fairly reasonable for development.

There are also development boards coming but it's likely you'll have
to wait til July for general availability and even then they will cost
$1000 and are not expected to have very good performance.  I notice
that avsm has signed up for one.

Rich.

             reply	other threads:[~2018-02-25 16:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-25 16:14 Richard W.M. Jones [this message]
2018-02-25 16:30 ` SP
2018-02-25 17:36   ` Richard W.M. Jones
2018-02-25 19:29 ` David Allsopp
2018-02-25 21:35   ` SP
2018-02-25 22:35     ` Nicolás Ojeda Bär
2018-02-26  8:56       ` Xavier Leroy
2018-02-26 14:13       ` SP
2018-02-26 14:20         ` Richard W.M. Jones

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=20180225161430.zkfpkihg7jyxs5cg@annexia.org \
    --to=rich@annexia.org \
    --cc=caml-list@inria.fr \
    --cc=nicolas.ojeda.bar@lexifi.com \
    /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).