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 1C6737FA80 for ; Fri, 23 Oct 2015 15:57:39 +0200 (CEST) IronPort-PHdr: 9a23:HPLq/BBCV6oV6F4WwfkKUyQJP3N1i/DPJgcQr6AfoPdwSP78pMbcNUDSrc9gkEXOFd2CrakU1qyO7eu+CCQp2tWojjMrSNR0TRgLiMEbzUQLIfWuLgnFFsPsdDEwB89YVVVorDmROElRH9viNRWJ+iXhpQAbFhi3DwdpPOO9QteU1JTqkbjssMOCKyxzxxODIppKZC2sqgvQssREyaBDEY0WjiXzn31TZu5NznlpL1/A1zz158O34YIxu38I46FppIZ8VvCwdK09SflcDS86G2Ez/szi8xfZB0Pb7XIZViASkwFUKwnD9hDzGJnr5HjUrO14jWOhOsD5UaozQXDqyqZgSBbljG1PYzs4+2Heh8g2l6VWrw67oARXwojIbYXTP/17KPCONegGTHZMC54CHxdKBZmxOtMC Authentication-Results: mail3-smtp-sop.national.inria.fr; spf=None smtp.pra=michael.soegtrop@intel.com; spf=Pass smtp.mailfrom=michael.soegtrop@intel.com; spf=None smtp.helo=postmaster@mga02.intel.com Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of michael.soegtrop@intel.com) identity=pra; client-ip=134.134.136.20; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="michael.soegtrop@intel.com"; x-sender="michael.soegtrop@intel.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail3-smtp-sop.national.inria.fr: domain of michael.soegtrop@intel.com designates 134.134.136.20 as permitted sender) identity=mailfrom; client-ip=134.134.136.20; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="michael.soegtrop@intel.com"; x-sender="michael.soegtrop@intel.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@mga02.intel.com) identity=helo; client-ip=134.134.136.20; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="michael.soegtrop@intel.com"; x-sender="postmaster@mga02.intel.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A0CMAABtPCpWnBSIhoZegmmBIW8GviUBDSOBNhcBAYYEAoE8OBQBAQEBAQEBARABAQEBAQYNCQkhIwuCK4IJBS0cQgEMDAIQVhcBDgEEG4gnAaMXok0thnmJWIJmDEMdgRQFlisBeahKHwEBgmmBXHKFPYEGAQEB X-IPAS-Result: A0CMAABtPCpWnBSIhoZegmmBIW8GviUBDSOBNhcBAYYEAoE8OBQBAQEBAQEBARABAQEBAQYNCQkhIwuCK4IJBS0cQgEMDAIQVhcBDgEEG4gnAaMXok0thnmJWIJmDEMdgRQFlisBeahKHwEBgmmBXHKFPYEGAQEB X-IronPort-AV: E=Sophos;i="5.20,186,1444687200"; d="scan'208,217";a="151561351" Received: from mga02.intel.com ([134.134.136.20]) by mail3-smtp-sop.national.inria.fr with ESMTP; 23 Oct 2015 15:57:36 +0200 Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga101.jf.intel.com with ESMTP; 23 Oct 2015 06:57:35 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.20,186,1444719600"; d="scan'208,217";a="833453435" Received: from irsmsx101.ger.corp.intel.com ([163.33.3.153]) by orsmga002.jf.intel.com with ESMTP; 23 Oct 2015 06:57:35 -0700 Received: from irsmsx102.ger.corp.intel.com ([169.254.2.98]) by IRSMSX101.ger.corp.intel.com ([169.254.1.33]) with mapi id 14.03.0248.002; Fri, 23 Oct 2015 14:57:33 +0100 From: "Soegtrop, Michael" To: "caml-list@inria.fr" Thread-Topic: Effect of Windows LLP64 architecture on 64 bit MingW OCaml Thread-Index: AdENmsKQlrGb4SdjTW+mxn2nfuieSg== Date: Fri, 23 Oct 2015 13:57:32 +0000 Message-ID: <0F7D3B1B3C4B894D824F5B822E3E5A172CE32E38@IRSMSX102.ger.corp.intel.com> Accept-Language: de-DE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [163.33.239.181] Content-Type: multipart/alternative; boundary="_000_0F7D3B1B3C4B894D824F5B822E3E5A172CE32E38IRSMSX102gercor_" MIME-Version: 1.0 Subject: [Caml-list] Effect of Windows LLP64 architecture on 64 bit MingW OCaml --_000_0F7D3B1B3C4B894D824F5B822E3E5A172CE32E38IRSMSX102gercor_ Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Dear Ocaml Users, I wonder what differences exist between a 64 bit Linux Ocaml and a 64 bit M= ingW Ocaml. 64bit Windows and MingW64 are what is called LLP64, that is int= and long are 32 bit and only long long, size_t and pointers are 64 bit as = in 32 bit Windows. MingW has to follow this convention, otherwise it would = be incompatible to the Windows headers. But 64 bit Linux tends to be LP64, = that is int is 32 bit, but long is 64 bit. The Ocaml C code doesn't seem to= use size abstraction types (like int32, int64), so I wonder what effect th= is has. Is a 64 bit MingW Ocaml somehow half 32 bit and half 64 bit as Ming= W C, or does it behave in the same way as a 64 bit Linux Ocaml? If MingW64 = bit Ocaml is equivalent to Linux64 Ocaml, it would be interesting to know h= ow this is done (there are a lot of longs e.g. in byterun). Best regards, Michael Intel Deutschland GmbH Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de Managing Directors: Christin Eisenschmid, Prof. Dr. Hermann Eul Chairperson of the Supervisory Board: Tiffany Doon Silva Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928 --_000_0F7D3B1B3C4B894D824F5B822E3E5A172CE32E38IRSMSX102gercor_ Content-Type: text/html; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable

Dear Ocaml Users,

 

I wonder what differences exist between a 64 bit Lin= ux Ocaml and a 64 bit MingW Ocaml. 64bit Windows and MingW64 are what is ca= lled LLP64, that is int and long are 32 bit and only long long, size_t and = pointers are 64 bit as in 32 bit Windows. MingW has to follow this convention, otherwise it would be incompatible to= the Windows headers. But 64 bit Linux tends to be LP64, that is int is 32 = bit, but long is 64 bit. The Ocaml C code doesn’t seem to use size ab= straction types (like int32, int64), so I wonder what effect this has. Is a 64 bit MingW Ocaml somehow half 32 bit= and half 64 bit as MingW C, or does it behave in the same way as a 64 bit = Linux Ocaml? If MingW64 bit Ocaml is equivalent to Linux64 Ocaml, it would = be interesting to know how this is done (there are a lot of longs e.g. in byterun).

 

Best regards,

 

Michael

Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Christin Eisenschmid, Prof. Dr. Hermann Eul
Chairperson of the Supervisory Board: Tiffany Doon Silva
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928

--_000_0F7D3B1B3C4B894D824F5B822E3E5A172CE32E38IRSMSX102gercor_--