From: Christoph Cullmann <cullmann@absint.de>
To: caml-list@yquem.inria.fr
Subject: OCaml + mingw-w64
Date: Mon, 22 Nov 2010 13:03:58 +0100 [thread overview]
Message-ID: <201011221303.58505.cullmann@absint.de> (raw)
Hi,
atm we compile out large ocaml application (Astree, http://www.astree.ens.fr/)
with ocaml + MSVC64.
I would like to go away from MSVC to mingw, to e.g. have gdb available and
more unix like environment.
Atm it seems only the normal mingw (32bit) is supported.
I found some problem with using the 64bit version with flexlinker, which I
reported to Alain Frisch to get that sorted out.
Aside from that, I think a problem might be, that there is no matching
assembler for amd64 + mingw (windows calling convention).
Is that correct and could somebody help me out with this?
I think, given that gcc on unices with 64bit work fine here, it shouldn't be
too much effort to get mingw-w64 working too, enabling to have a nice (and fast
for the bytecode interpreter) variant of ocaml for win64 using mostly open
source components ;)
Other feedback (which is valid for MSVC64, too):
In ocaml 3.12, in byterun/major_gc.h, there is:
intnat caml_major_collection_slice (long howmuch)
whereas in the .c file that is:
intnat caml_major_collection_slice (intnat howmuch)
As intnat is with mingw-w64 long long, this doesn't match.
Should not the header use intnat, too?
Greetings
Christoph
--
-------------------------------------- Christoph Cullmann ---------
AbsInt Angewandte Informatik GmbH Email: cullmann@AbsInt.com
Science Park 1 Tel: +49-681-38360-22
66123 Saarbrücken Fax: +49-681-38360-20
GERMANY WWW: http://www.AbsInt.com
--------------------------------------------------------------------
Geschäftsführung: Dr.-Ing. Christian Ferdinand
Eingetragen im Handelsregister des Amtsgerichts Saarbrücken, HRB 11234
reply other threads:[~2010-11-22 12:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201011221303.58505.cullmann@absint.de \
--to=cullmann@absint.de \
--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