From: "Richard W.M. Jones" <rich@annexia.org>
To: Nicolas Ojeda Bar <n.oje.bar@gmail.com>
Cc: caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] [ANN] RISC-V native backend, no longer cross-compiling
Date: Tue, 8 Nov 2016 19:08:49 +0000 [thread overview]
Message-ID: <20161108190849.GJ27249@annexia.org> (raw)
In-Reply-To: <CAPunWhCBeTyek8bjiHLvvH=gTLLPkhrEB12U7ptiQg=6Ky1VQg@mail.gmail.com>
On Sat, Nov 05, 2016 at 08:43:15AM +0100, Nicolas Ojeda Bar wrote:
> Today I am happy to announce a preliminary, native release of the full
> OCaml system on RISC-V. It is available at
>
> https://www.github.com/nojb/riscv-ocaml.
>
> It targets the 64-bit variant of the RISC-V architecture, RV64G (the
> 32-bit variant should also work, but has not been tested). All
> libraries are supported (Dynlink and Num have a couple of issues left,
> but I expect them to be resolved shortly).
>
> I plan to maintain and keep developing this port for the foreseeable
> future, tracking official OCaml releases. It is currently based on
> the recently released 4.04.0.
I have added your backend to the Fedora Rawhide OCaml 4.04.0 package.
It's not yet built in the publicly available Fedora/RISC-V packages,
since those are based on Fedora 25 [currently Rawhide is the future
Fedora 26]. However you can still look at the sources here:
http://pkgs.fedoraproject.org/cgit/rpms/ocaml.git/log/
http://pkgs.fedoraproject.org/cgit/rpms/ocaml-srpm-macros.git/log/
A couple of things which would help us (a little, although they are
not a big deal):
- Squash your patches down to a single commit ...
- ... but separate out the config.guess/config.sub change in
a separate commit, since we would usually copy those in
from our own copies.
Thanks for your great work on OCaml & RISC-V,
Rich.
next prev parent reply other threads:[~2016-11-08 19:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-05 7:43 Nicolas Ojeda Bar
2016-11-08 19:08 ` Richard W.M. Jones [this message]
2016-11-09 22:44 ` 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=20161108190849.GJ27249@annexia.org \
--to=rich@annexia.org \
--cc=caml-list@inria.fr \
--cc=n.oje.bar@gmail.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