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 mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by sympa.inria.fr (Postfix) with ESMTPS id C76077F7AF for ; Sun, 27 Sep 2015 02:55:41 +0200 (CEST) IronPort-PHdr: 9a23:C5W6xBYxEUAc/4qyFs7ghYX/LSx+4OfEezUN459isYplN5qZpc+5bnLW6fgltlLVR4KTs6sC0LqK9f24EUU7or+/81k6OKRWUBEEjchE1ycBO+WiTXPBEfjxciYhF95DXlI2t1uyMExSBdqsLwaK+i760zceF13FOBZvIaytQ8iJ35jxirj60qaQSjsLrQL1Wal1IhSyoFeZnegtqqwmFJwMzADUqGBDYeVcyDAgD1uSmxHh+pX4p8Y7oGwD884moulrWKD+N/AzRLlcSTAnKHwd5cvxtBCFQxHZtVUGVWBDqBNPHgyNwAz5U9+lqCL9q+5x8CafNMzyC7szXGLxvO9QVBb0hXJfZHYC+2bNh5kogQ== Authentication-Results: mail3-smtp-sop.national.inria.fr; spf=None smtp.pra=raould@gmail.com; spf=Pass smtp.mailfrom=raould@gmail.com; spf=None smtp.helo=postmaster@mail-oi0-f43.google.com Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of raould@gmail.com) identity=pra; client-ip=209.85.218.43; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="raould@gmail.com"; x-sender="raould@gmail.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail3-smtp-sop.national.inria.fr: domain of raould@gmail.com designates 209.85.218.43 as permitted sender) identity=mailfrom; client-ip=209.85.218.43; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="raould@gmail.com"; x-sender="raould@gmail.com"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of postmaster@mail-oi0-f43.google.com) identity=helo; client-ip=209.85.218.43; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="raould@gmail.com"; x-sender="postmaster@mail-oi0-f43.google.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A0D9AQCHPQdWlCvaVdFdhGEGqmKGY5NxAoEaBzsRAQEBAQEBAQEQAQEBAQcLCwkfMIIdgggBAQMBEhEdARseAwELBgULDwImAgIiAREBBQEcBjWHdgEDCgipWoEwPjGLR4FsgnmJVgoZJw1WhDYBAQgCARkBBQ6BFIVRhH2FFIJpgUMFjXSHfI0PmXMSI4EXN4Iwgh0eM4khAQEB X-IPAS-Result: A0D9AQCHPQdWlCvaVdFdhGEGqmKGY5NxAoEaBzsRAQEBAQEBAQEQAQEBAQcLCwkfMIIdgggBAQMBEhEdARseAwELBgULDwImAgIiAREBBQEcBjWHdgEDCgipWoEwPjGLR4FsgnmJVgoZJw1WhDYBAQgCARkBBQ6BFIVRhH2FFIJpgUMFjXSHfI0PmXMSI4EXN4Iwgh0eM4khAQEB X-IronPort-AV: E=Sophos;i="5.17,594,1437429600"; d="scan'208";a="148689295" Received: from mail-oi0-f43.google.com ([209.85.218.43]) by mail3-smtp-sop.national.inria.fr with ESMTP/TLS/AES128-GCM-SHA256; 27 Sep 2015 02:55:40 +0200 Received: by oiww128 with SMTP id w128so75054941oiw.2 for ; Sat, 26 Sep 2015 17:55:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=1BjxApqZDXjx/+5zTzadjOfeymLUEdvsF/IMz44x0gA=; b=Vx6Pg4YYKOzDW72ZHdjsDZzqSH2oc8GtP3IyrXSIV0AJNlrqV3Zyru0bO71Fif2nN4 PmrxAK6jODV/R7UiYTjYon22zLLSRXLtTjB6eBi9sZHTomvanW1AAYXZiP+bq66DLAKp 4yCLzMMwkhSnAzzDFptXrnqaVeUz7SDoyyTpTmIRt83eGvHidK1q/XlHTqHi7BV9NL5D LwjfHtJNm1WvJUNlVpFulFSW/jog5sqcXVcX2Zu56+IEcq6emM5nkfsK/Q4u7eNXytXN yGXVyLqXlBko5SC2ogyCx+qCCOe8jcqbs/q5y/tx+lMx/MtcYOed+bvVIz0PbJ18fcCn Km5Q== MIME-Version: 1.0 X-Received: by 10.202.4.198 with SMTP id 189mr6674103oie.93.1443315338847; Sat, 26 Sep 2015 17:55:38 -0700 (PDT) Received: by 10.182.172.36 with HTTP; Sat, 26 Sep 2015 17:55:38 -0700 (PDT) In-Reply-To: References: <1443259698.4442.12.camel@e130.lan.sumadev.de> Date: Sat, 26 Sep 2015 17:55:38 -0700 Message-ID: From: Raoul Duke To: OCaml Content-Type: text/plain; charset=UTF-8 Subject: Re: [Caml-list] whither portability? > Both ocamlc and ocamlopt work for iOS and Android; there is not really > a good reason to use the bytecode compiler for deployment to mobile. > > There is no such thing as "LLVM bytecode" and LLVM bitcode (sic) > is merely an intermediate format for native executable code. Shipping > LLVM bitcode offers no conceptual improvement over shipping > machine code and in any case, there is neither an LLVM backend > for ocamlopt nor much need for such a backend. Yes, "bitcode" is the right term. It is now the format Apple wants. So I dunno why people would actively discount it here.