From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@sympa.inria.fr Delivered-To: caml-list@sympa.inria.fr Received: from mail4-relais-sop.national.inria.fr (mail4-relais-sop.national.inria.fr [192.134.164.105]) by sympa.inria.fr (Postfix) with ESMTPS id A35E97EEAF for ; Wed, 16 Jan 2013 23:32:55 +0100 (CET) Received-SPF: None (mail4-smtp-sop.national.inria.fr: no sender authenticity information available from domain of benedikt.meurer@googlemail.com) identity=pra; client-ip=209.85.214.53; receiver=mail4-smtp-sop.national.inria.fr; envelope-from="benedikt.meurer@googlemail.com"; x-sender="benedikt.meurer@googlemail.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail4-smtp-sop.national.inria.fr: domain of benedikt.meurer@googlemail.com designates 209.85.214.53 as permitted sender) identity=mailfrom; client-ip=209.85.214.53; receiver=mail4-smtp-sop.national.inria.fr; envelope-from="benedikt.meurer@googlemail.com"; x-sender="benedikt.meurer@googlemail.com"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail4-smtp-sop.national.inria.fr: no sender authenticity information available from domain of postmaster@mail-bk0-f53.google.com) identity=helo; client-ip=209.85.214.53; receiver=mail4-smtp-sop.national.inria.fr; envelope-from="benedikt.meurer@googlemail.com"; x-sender="postmaster@mail-bk0-f53.google.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Aq8BAI8p91DRVdY1k2dsb2JhbABEvX8WDgEBAQEJCQsJFAQjgh4BAQMBAToGATgBAwELBgULDRwSNAEFARwGE4gGAQMJBgQIm3+PL4UHCkANiAoBBQyLfIRPYQOWDI5oP4QY X-IronPort-AV: E=Sophos;i="4.84,481,1355094000"; d="scan'208";a="168715549" Received: from mail-bk0-f53.google.com ([209.85.214.53]) by mail4-smtp-sop.national.inria.fr with ESMTP/TLS/RC4-SHA; 16 Jan 2013 23:32:52 +0100 Received: by mail-bk0-f53.google.com with SMTP id j5so1003643bkw.40 for ; Wed, 16 Jan 2013 14:32:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=KtqJUbUKUQ7nvymgeuYlXWHltbLeFB4Me2zD3unHQ/M=; b=EKcrR+3yBCu9cIkZ/4wMZqrI/UnQooB+Cf0gksdDKh68DmmOKe+osYflzcVU3JkEfF 07oSfhE2+r5QAYR39EG1hvjhvrGKmDColNvYhCXVXHSJ2nl9O1HeVNKMI4BGPy0RUOzx /bWEtukkzU1lwIv9XLghg1hlZeP2UR79SwUA4mBE8HmLlaQyic6kFhpVTUBhqWqJZzpi JU64rTLEsWGBeHAA0p16Z4GJ7z0szIKLCTQ/bZnAq8n7bDxVT/Dfz5g4DIoHUzUlZCtD cUO2EW87KZz81+QAf5qRdAWjD5mnHkyRe5w4IMRU2hssRNwxOSfoNtQ0FJuloavXBzDA kC0A== X-Received: by 10.204.149.12 with SMTP id r12mr924497bkv.30.1358375571383; Wed, 16 Jan 2013 14:32:51 -0800 (PST) Received: from tatooine.in.benediktmeurer.de (sign-4db6a582.pool.mediaWays.net. [77.182.165.130]) by mx.google.com with ESMTPS id m20sm16991074bkw.4.2013.01.16.14.32.49 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 16 Jan 2013 14:32:50 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) From: Benedikt Meurer In-Reply-To: <20130116094800.GA9538@ours.starynkevitch.net> Date: Wed, 16 Jan 2013 23:32:53 +0100 Cc: Gerd Stolpmann , Francois Berenger , caml-list@inria.fr Content-Transfer-Encoding: quoted-printable Message-Id: <610FAC34-EFC6-411F-87B7-03CA021E5C8E@gmail.com> References: <43fbc889-f7fc-4bd6-949b-634d478326f6@googlegroups.com> <50F66B57.3070601@riken.jp> <1358326866.28639.13@samsung> <20130116094800.GA9538@ours.starynkevitch.net> To: Basile Starynkevitch X-Mailer: Apple Mail (2.1499) Subject: Re: [Caml-list] ocamlc compiles hello world, ocamlopt not On Jan 16, 2013, at 10:48 , Basile Starynkevitch = wrote: > On Wed, Jan 16, 2013 at 10:01:06AM +0100, Gerd Stolpmann wrote: >> Am 16.01.2013 09:56:55 schrieb(en) Francois Berenger: >>> On 01/16/2013 05:02 PM, r0ller@freemail.hu wrote: >>>> Hi All, >>>>=20 >>>> By the way, is there any doc available about porting ocaml >>>> (google didn't find any) or any hint on how to move forward? I'd >>>> really like to have the native compiler on minix too. >>>=20 >>> I think in the past it was possible to generate C code from OCaml >>> code. >>=20 >> There is no real C backend (and has never been). The only thing you >> can do is to embed bytecode in a C-friendly way (what -output-obj >> does). But it is still bytecode. >=20 > Benoit Vaugon & Michel Mauny worked recently on OcamlCC > (a translator from Ocaml bytecode to C) > http://oud.ocaml.org/2012/abstracts/oud2012-final10.pdf > https://github.com/ocaml-bytes/ocamlcc Very interesting work. I somehow missed that so far. I did something simila= r prior to starting with OCamlJIT2, but that turned out to be very slow wit= h the compilation of the C code. I'd be interested to hear about results fr= om generating LLVM code instead of C. Actually I'm still thinking that a tr= acing JIT using LLVM to optimize/generate code could be a viable option for= the bytecode runtime (this is one of the results we gathered while working= on Colin's thesis, the LLVM backend for the native code compiler). greets, Benedikt=