From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <berenger@riken.jp>
X-Original-To: caml-list@sympa.inria.fr
Delivered-To: caml-list@sympa.inria.fr
Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83])
	by sympa.inria.fr (Postfix) with ESMTPS id 106CA7EEAF
	for <caml-list@sympa.inria.fr>; Fri,  1 Feb 2013 08:53:51 +0100 (CET)
Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender
  authenticity information available from domain of
  berenger@riken.jp) identity=pra; client-ip=134.160.33.176;
  receiver=mail2-smtp-roc.national.inria.fr;
  envelope-from="berenger@riken.jp";
  x-sender="berenger@riken.jp"; x-conformance=sidf_compatible
Received-SPF: Pass (mail2-smtp-roc.national.inria.fr: domain of
  berenger@riken.jp designates 134.160.33.176 as permitted
  sender) identity=mailfrom; client-ip=134.160.33.176;
  receiver=mail2-smtp-roc.national.inria.fr;
  envelope-from="berenger@riken.jp";
  x-sender="berenger@riken.jp"; x-conformance=sidf_compatible;
  x-record-type="v=spf1"
Received-SPF: Pass (mail2-smtp-roc.national.inria.fr: domain of
  postmaster@postman.riken.jp designates 134.160.33.176 as
  permitted sender) identity=helo; client-ip=134.160.33.176;
  receiver=mail2-smtp-roc.national.inria.fr;
  envelope-from="berenger@riken.jp";
  x-sender="postmaster@postman.riken.jp";
  x-conformance=sidf_compatible; x-record-type="v=spf1"
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvABAPBzC1GGoCGwmWdsb2JhbABFgzm6YwQEgRYOAQEBAQEICwsHFCeCHgEBBThBEAsSBgklDwI4DhMBBQIBAYgNwi6NY4MpA4hjjTGFcI1o
X-IPAS-Result: AvABAPBzC1GGoCGwmWdsb2JhbABFgzm6YwQEgRYOAQEBAQEICwsHFCeCHgEBBThBEAsSBgklDwI4DhMBBQIBAYgNwi6NY4MpA4hjjTGFcI1o
X-IronPort-AV: E=Sophos;i="4.84,579,1355094000"; 
   d="scan'208";a="935510"
Received: from postman4.riken.jp (HELO postman.riken.jp) ([134.160.33.176])
  by mail2-smtp-roc.national.inria.fr with ESMTP; 01 Feb 2013 08:53:49 +0100
Received: from postman.riken.jp (postman4.riken.jp [127.0.0.1])
	by postman.riken.jp (Postfix) with SMTP id 923128280E5;
	Fri,  1 Feb 2013 16:53:44 +0900 (JST)
Received: from [172.27.98.103] (rikad98.riken.jp [134.160.214.98])
	by postman.riken.jp (Postfix) with ESMTPA id DE2C27F8046;
	Fri,  1 Feb 2013 16:53:43 +0900 (JST)
Message-ID: <510B7487.90708@riken.jp>
Date: Fri, 01 Feb 2013 16:53:43 +0900
From: Francois Berenger <berenger@riken.jp>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: oleg@okmij.org
CC: rixed@happyleptic.org, caml-list@inria.fr
References: <20130201065335.44274.qmail@www1.g3.pair.com>
In-Reply-To: <20130201065335.44274.qmail@www1.g3.pair.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-PMX-Version: 5.6.0.2009776, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.2.1.74216
Subject: Re: [Caml-list] ANN: Brand-new BER MetaOCaml for OCaml 4.00.1

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.