From: Xavier Leroy <Xavier.Leroy@inria.fr>
To: Fritz Anderson <fritza@uchicago.edu>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Compiling for Mac OS 64 bit?
Date: Thu, 27 Oct 2005 17:21:43 +0200 [thread overview]
Message-ID: <4360F087.8030008@inria.fr> (raw)
In-Reply-To: <3B352EDD-F1A3-4934-9A0E-53095B258E05@uchicago.edu>
> I've been asked to research the use of Ocaml in high-performance
> computing applications on Mac OS X. I take this to mean (a) 64-bit
> applications (the client says so) and (b) compiled applications.
As you found out, ocamlopt currently cannot generate PPC64 code.
So, it's either bytecode-only in 64-bit mode, or native code in 32-bit
mode.
A PPC64 port of ocamlopt looks reasonably simple, but that will have
to wait until a Mac G5 lands here at INRIA.
> Make opt is not so happy. One example is that the assembler balks at
>
> _camlPervasives__55:
> .long _caml_int64_ops
> .long 1018167296
> .long 4372995238176751616
> .data
> .long 2303
>
> because the huge number should take the .quad directive, not .long. But
> given that the huge number is 0x3cb0000000000000, I have bad feelings
> that this is some badly-cleared or -shifted native integer.
No, no, it's a genuine 64-bit integer constant (see the definition of
epsilon_float in stdlib/pervasives.ml).
> In fact, my
> skimming of the compiler source suggests that the compiler doesn't do
> native 64-bit pointers and integers.
The PowerPC back-end does not, but everything else in OCaml will
gladly handle 64-bit quantities on a 64-bit architecture (e.g. Alpha,
AMD64, IA64).
- Xavier Leroy
next prev parent reply other threads:[~2005-10-27 15:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-25 16:37 Fritz Anderson
2005-10-27 15:21 ` Xavier Leroy [this message]
2005-10-27 21:59 [Caml-list] " Gregory Lafitte
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=4360F087.8030008@inria.fr \
--to=xavier.leroy@inria.fr \
--cc=caml-list@yquem.inria.fr \
--cc=fritza@uchicago.edu \
/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).