From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail1-relais-roc.national.inria.fr (mail1-relais-roc.national.inria.fr [192.134.164.82]) by sympa.inria.fr (Postfix) with ESMTPS id 407947ED7A for ; Mon, 3 Sep 2012 21:42:00 +0200 (CEST) Received-SPF: None (mail1-smtp-roc.national.inria.fr: no sender authenticity information available from domain of bobzhang1988@gmail.com) identity=pra; client-ip=209.85.210.182; receiver=mail1-smtp-roc.national.inria.fr; envelope-from="bobzhang1988@gmail.com"; x-sender="bobzhang1988@gmail.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail1-smtp-roc.national.inria.fr: domain of bobzhang1988@gmail.com designates 209.85.210.182 as permitted sender) identity=mailfrom; client-ip=209.85.210.182; receiver=mail1-smtp-roc.national.inria.fr; envelope-from="bobzhang1988@gmail.com"; x-sender="bobzhang1988@gmail.com"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail1-smtp-roc.national.inria.fr: no sender authenticity information available from domain of postmaster@mail-iy0-f182.google.com) identity=helo; client-ip=209.85.210.182; receiver=mail1-smtp-roc.national.inria.fr; envelope-from="bobzhang1988@gmail.com"; x-sender="postmaster@mail-iy0-f182.google.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AkgBAH4HRVDRVdK2mGdsb2JhbABFuxsIIgEBAQEBCAkNBxQnghciAiwBGx4DEggBB10BEQEFARYMNYdbAQMMmRCCYQkDjCOCc4R0ChknDVmIcwEFDJIkA5VZjjw+hB8 X-IronPort-AV: E=Sophos;i="4.80,361,1344204000"; d="scan'208";a="171726054" Received: from mail-iy0-f182.google.com ([209.85.210.182]) by mail1-smtp-roc.national.inria.fr with ESMTP/TLS/RC4-SHA; 03 Sep 2012 21:41:59 +0200 Received: by ialo14 with SMTP id o14so14032773ial.27 for ; Mon, 03 Sep 2012 12:41:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=apvLoOtFJAOFvNqbmjG+Vmj2oSFwfRf5UqApu4tx1xc=; b=Pp4EkEW4UoXR4Z28RQNP3wMA5RxuZEjDguoOd4Gmi5KdyBzl2p2IKfUPsf21jLdMUF aO+paEwSgg/b3aiU2fPSqiGDRK6F15w01pdKVEIVeLwOj/XfEFJHJbbxk7qEGtKLphcQ sZyhRY3VUay+zgJu6lgh4SAnH4xu1/KMTtVI39tx1iizdTGkCuLVHxKCqV85WiNtgxYM rgFWrCZ679dumJNp9Xh6CAPqdbrp7/+ev/gQIYFUPSNUddM1oL/u6VZ6aNCC0inETTuj WWr3qSZvxcRVD9cN0iTzuHyDWHMK3JLr3bPTPw8IiTE69EsHszSALAa+xrJ32PHmbS1Q iDDA== MIME-Version: 1.0 Received: by 10.50.57.202 with SMTP id k10mr4136469igq.45.1346701318514; Mon, 03 Sep 2012 12:41:58 -0700 (PDT) Received: by 10.64.166.34 with HTTP; Mon, 3 Sep 2012 12:41:58 -0700 (PDT) Date: Mon, 3 Sep 2012 15:41:58 -0400 Message-ID: From: bob zhang To: Caml List Content-Type: multipart/alternative; boundary=14dae9340fb5b566f304c8d15598 Subject: [Caml-list] bootstrapping for ocaml's compiler --14dae9340fb5b566f304c8d15598 Content-Type: text/plain; charset=ISO-8859-1 Hi List, Can anyone tell me that ocaml's native code bootstrapping system can reach a fixpoint or not? I am doing my own compiler using ocaml as backend,* I found something weird: the byte-code * *compiler can always reach a fix-point, the native-code can reach a fix-point sometimes, sometimes not.* *Is this expected behavior or not? Is there any randomized algorithm used in ocamlopt?* Many thanks! -- Regards -- Bob --14dae9340fb5b566f304c8d15598 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi List,
=A0 =A0Can anyone tell me that ocaml's native code bootstr= apping system can reach a fixpoint or not?
I am doing my own comp= iler using ocaml as backend, I found something weird: the byte-code= =A0
compiler can always reach a fix-point, the native-code can reach= a fix-point sometimes, sometimes not.
Is this expe= cted behavior or not? Is there any randomized algorithm used in ocamlopt?

=A0 =A0Many thanks!

-- =
Regards
-- Bob
--14dae9340fb5b566f304c8d15598--