From: Xavier Leroy <Xavier.Leroy@inria.fr>
To: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] Status of the OCaml RISC-V port
Date: Mon, 26 Feb 2018 08:56:35 +0000 [thread overview]
Message-ID: <CAH=h3gGbM1_VhiRzy9JW1P4aoYh2AiKcxqJaO8sHGkvV02xPuA@mail.gmail.com> (raw)
In-Reply-To: <CADK7aFPKdZKrNrj4+wMcVT0xZGU5Hz_ERprtoXZ_an1MTQv2yw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1144 bytes --]
On Sun, Feb 25, 2018 at 11:36 PM Nicolás Ojeda Bär <
nicolas.ojeda.bar@lexifi.com> wrote:
>
> When the time comes, the patch will be submitted as a github PR and
> everyone is warmly invited to take part in that discussion.
>
>
Absolutely. Just to reinforce what's been said already: there is no doubt
in my mind that the RISC-V back-end will be part of the core OCaml
distribution. What is not completely decided is when it will be merged.
I'm looking forward to playing with the first RISC-V hardware
implementation, thanks to OCaml Labs. It's good to know about the
QEMU-based virtual environment mentioned by Rich Jones.
- Xavier Leroy
> And of course, PRs are also welcome anytime at
> https://github.com/nojb/riscv-ocaml !
>
> Best wishes,
> Nicolás
>
>
> On Sun, Feb 25, 2018 at 10:35 PM, SP <sp@orbitalfox.eu> wrote:
>
>>
>>
>> On 25 February 2018 19:29:45 GMT+00:00, David Allsopp <
>> dra-news@metastack.com> wrote:
>> >will hopefully start the process of upstreaming the RISC-V patches.
>>
>> Will you be looking for help from the wider community for this?
>>
>> --
>> SP
>>
>
>
[-- Attachment #2: Type: text/html, Size: 2176 bytes --]
next prev parent reply other threads:[~2018-02-26 8:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-25 16:14 Richard W.M. Jones
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 [this message]
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='CAH=h3gGbM1_VhiRzy9JW1P4aoYh2AiKcxqJaO8sHGkvV02xPuA@mail.gmail.com' \
--to=xavier.leroy@inria.fr \
--cc=caml-list@inria.fr \
/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).