From: "Olivier Andrieu" <oandrieu@nerim.net>
To: malc <av1474@comtv.ru>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] caml_alloc + 64 bits - caml_alloc.h
Date: Tue, 13 Jan 2009 11:26:36 +0100 [thread overview]
Message-ID: <95513600901130226j636b7930kce59e050c943e2a2@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0901131232550.2161@linmac.oyster.ru>
On Tue, Jan 13, 2009 at 10:37, malc <av1474@comtv.ru> wrote:
> P.S. This whole value->intnat->long makes me wonder how OCaml is
> ever supposed to work on LLP64...
It does already, since 3.10. From byterun/config.h :
/* Win64 model: IL32LLP64 */
typedef ARCH_INT64_TYPE intnat;
where ARC_INT64_TYPE is either long long or __in64 depending on the
compiler (GCC or MSVC).
--
Olivier
prev parent reply other threads:[~2009-01-13 10:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-13 4:51 Daniel de Rauglaudre
2009-01-13 4:58 ` [Caml-list] " Erik de Castro Lopo
2009-01-13 5:15 ` Daniel de Rauglaudre
2009-01-13 9:37 ` malc
2009-01-13 10:26 ` Olivier Andrieu [this message]
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=95513600901130226j636b7930kce59e050c943e2a2@mail.gmail.com \
--to=oandrieu@nerim.net \
--cc=av1474@comtv.ru \
--cc=caml-list@inria.fr \
/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).