From: Anil Madhavapeddy <anil@recoil.org>
To: Francois Berenger <berenger@riken.jp>
Cc: oleg@okmij.org, rixed@happyleptic.org, caml-list@inria.fr
Subject: Re: [Caml-list] ANN: Brand-new BER MetaOCaml for OCaml 4.00.1
Date: Tue, 26 Feb 2013 18:09:52 +0000 [thread overview]
Message-ID: <8D005CC4-A79A-4C6A-ABC0-5E152C2EB402@recoil.org> (raw)
In-Reply-To: <510B7487.90708@riken.jp>
On 1 Feb 2013, at 07:53, Francois Berenger <berenger@riken.jp> wrote:
> On 02/01/2013 03:53 PM, oleg@okmij.org wrote:
>> Francois Berenger wrote:
>>> Could it be (ab)used to translate easily a whole program's OCaml source
>>> into C code?
>>
>> In fact at one point MetaOCaml did so -- translated the generated OCaml
>> code to C or Fortran. This feature -- called offshoring -- was used to
>> generate FFT kernels. The generated C code was good enough to plug as
>> it was into the FFTW benchmarking and testing framework. During the
>> overhaul offshoring has been separated and left for clean-up and
>> re-writing. Now there is a place for it in the overall architecture.
>
> Amazing.
> At some point, if MetaOcaml can be made available as an OPAM switch,
> people will be able to give it a try very easily.
Thanks to Cedric Cellier packaging it up and sending us a pull request [1],
you can try our MetaOCaml BER straight from OPAM via:
$ opam update
$ opam switch 4.00.1+BER
$ eval `opam config env`
$ ocaml...
-anil
[1] https://github.com/OCamlPro/opam-repository/pull/461
next prev parent reply other threads:[~2013-02-26 18:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-01 6:53 oleg
2013-02-01 7:53 ` Francois Berenger
2013-02-26 18:09 ` Anil Madhavapeddy [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-02-19 3:37 bob zhang
2013-02-20 1:51 ` Jacques Carette
2013-02-20 14:03 ` bob zhang
2013-01-31 7:49 oleg
2013-01-31 12:23 ` rixed
2013-02-01 2:12 ` Francois Berenger
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=8D005CC4-A79A-4C6A-ABC0-5E152C2EB402@recoil.org \
--to=anil@recoil.org \
--cc=berenger@riken.jp \
--cc=caml-list@inria.fr \
--cc=oleg@okmij.org \
--cc=rixed@happyleptic.org \
/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).