From: Fritz Anderson <fritza@uchicago.edu>
To: caml-list@yquem.inria.fr
Subject: Compiling for Mac OS 64 bit?
Date: Tue, 25 Oct 2005 11:37:18 -0500 [thread overview]
Message-ID: <3B352EDD-F1A3-4934-9A0E-53095B258E05@uchicago.edu> (raw)
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.
I've configured the build with
./configure -cc 'gcc -arch ppc64' -tk-no-x11
... which seems to produce the interpreter with no complaints, with
the only exception that ocamlmklib.ml had to be edited so that '-arch
ppc64' was appended to the value of the mksharedlib variable. Make
bootstrap concludes without error.
(Caveats that an interpreter that has to haul 64-bit entities around
instead of 32-bit entities is apt to be slower, are already
understood. By me. The client sees a knob labeled 32/64, and wants to
turn it all the way up.)
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.
In fact, my skimming of the compiler source suggests that the
compiler doesn't do native 64-bit pointers and integers.
Is there a way to configure Ocaml to produce a 64-bit compiler, or is
there a project for one? (I know, I'm asking for magic beans.) Or do
I tell the client that on PowerPC/Mac OS, it's 32 bits or nothing?
-- F
Fritz Anderson
Mac Programmer
University of Chicago
next reply other threads:[~2005-10-25 16:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-25 16:37 Fritz Anderson [this message]
2005-10-27 15:21 ` [Caml-list] " Xavier Leroy
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=3B352EDD-F1A3-4934-9A0E-53095B258E05@uchicago.edu \
--to=fritza@uchicago.edu \
--cc=caml-list@yquem.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