caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: skaller <skaller@users.sourceforge.net>
To: Niall Dalton <niall@xrnd.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Re: 64 bit windows
Date: Thu, 08 Sep 2005 06:51:31 +1000	[thread overview]
Message-ID: <1126126291.28300.13.camel@rosella.wigram> (raw)
In-Reply-To: <431EFAEF.9020209@xrnd.com>

[-- Attachment #1: Type: text/plain, Size: 1030 bytes --]

On Wed, 2005-09-07 at 15:36 +0100, Niall Dalton wrote:
> Hello,
> 
> I wrote rather in haste yesterday, so perhaps my message was less than 
> understandable, apologies!
> 
> I'm wondering if there is any plan for native code compilation on 64 bit 
> windows using the Visual Studio toolchain? Microsoft do ship a 64 bit 
> assembler with it (at least in VC2005 beta and the DDK). However, they 
> have defined 'long' as 32 bits rather than the more usual 64 bits on a 
> 64 bit OS. Are there any other particular 'gotchas' preventing a 
> 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 
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.

-- 
John Skaller <skaller at users dot sourceforge dot net>


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-09-07 20:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-06 15:31 64 windows caml Niall Dalton
2005-09-07 14:36 ` 64 bit windows Niall Dalton
2005-09-07 20:51   ` skaller [this message]
2005-09-08  7:50     ` [Caml-list] " Ville-Pertti Keinonen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1126126291.28300.13.camel@rosella.wigram \
    --to=skaller@users.sourceforge.net \
    --cc=caml-list@inria.fr \
    --cc=niall@xrnd.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).