From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@yquem.inria.fr Delivered-To: caml-list@yquem.inria.fr Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39]) by yquem.inria.fr (Postfix) with ESMTP id E8401BDCB for ; Wed, 7 Sep 2005 22:51:46 +0200 (CEST) Received: from pauillac.inria.fr (pauillac.inria.fr [128.93.11.35]) by concorde.inria.fr (8.13.0/8.13.0) with ESMTP id j87KpkDh012711 for ; Wed, 7 Sep 2005 22:51:46 +0200 Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39]) by pauillac.inria.fr (8.7.6/8.7.3) with ESMTP id WAA28215 for ; Wed, 7 Sep 2005 22:51:45 +0200 (MET DST) Received: from ash25e.internode.on.net (ash25e.internode.on.net [203.16.214.182]) by concorde.inria.fr (8.13.0/8.13.0) with ESMTP id j87Kphk9012702 for ; Wed, 7 Sep 2005 22:51:44 +0200 Received: from rosella (ppp32-47.lns1.syd6.internode.on.net [59.167.32.47]) by ash25e.internode.on.net (8.12.9/8.12.6) with ESMTP id j87KpVfL058471; Thu, 8 Sep 2005 06:21:41 +0930 (CST) (envelope-from skaller@users.sourceforge.net) Subject: Re: [Caml-list] Re: 64 bit windows From: skaller To: Niall Dalton Cc: caml-list@inria.fr In-Reply-To: <431EFAEF.9020209@xrnd.com> References: <431DB63E.8070909@xrnd.com> <431EFAEF.9020209@xrnd.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-Yt31GufvW8rTTRr86gCf" Date: Thu, 08 Sep 2005 06:51:31 +1000 Message-Id: <1126126291.28300.13.camel@rosella.wigram> Mime-Version: 1.0 X-Mailer: Evolution 2.2.1.1 X-Miltered: at concorde with ID 431F52E2.000 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! X-Miltered: at concorde with ID 431F52DF.000 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! X-Spam: no; 0.00; caml-list:01 compilation:01 vastly:01 wrote:01 wrote:01 sourceforge:01 sourceforge:01 unix:01 integer:01 ints:01 ints:01 defined:01 native:02 assembler:02 gnu:03 X-Attachments: type="application/pgp-signature" name="signature.asc" X-Spam-Checker-Version: SpamAssassin 3.0.3 (2005-04-27) on yquem.inria.fr X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=disabled version=3.0.3 --=-Yt31GufvW8rTTRr86gCf Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Wed, 2005-09-07 at 15:36 +0100, Niall Dalton wrote: > Hello, >=20 > I wrote rather in haste yesterday, so perhaps my message was less than=20 > understandable, apologies! >=20 > I'm wondering if there is any plan for native code compilation on 64 bit=20 > windows using the Visual Studio toolchain? Microsoft do ship a 64 bit=20 > assembler with it (at least in VC2005 beta and the DDK). However, they=20 > have defined 'long' as 32 bits rather than the more usual 64 bits on a=20 > 64 bit OS. Are there any other particular 'gotchas' preventing a=20 > straightforward port? Actually MS decision is vastly more sensible than the gnu choice: it leaves all the ints the same size on win32 and win64, so all strictly conforming code will continue to work the same=20 way, right up to integer overflow, bit masks, etc. The real 'gotcha' is the Unix programmers that decided it was OK to use 32 bit ints as addresses .. their code will break under both models. --=20 John Skaller --=-Yt31GufvW8rTTRr86gCf Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQBDH1LTsRp8/9aGVGsRAuuEAJ94QSQmZW5E7IAa6HWjiqCygHbdCQCfWX1t Ghqkg8vjAKIt2Q00QZLX0xk= =LB5S -----END PGP SIGNATURE----- --=-Yt31GufvW8rTTRr86gCf--