From: William Chesters <williamc@dai.ed.ac.uk>
To: karine CHEVALIER-JABET <jabet@baobab1.cad.cea.fr>
Cc: caml-list@inria.fr
Subject: interfacing FORTRAN/OCAML??
Date: Wed, 1 Sep 1999 15:24:07 +0100 [thread overview]
Message-ID: <199909011424.PAA03347@toy.william.bogus> (raw)
In-Reply-To: <37CA7F0C.5ABA5136@baobab1.cad.cea.fr>
karine CHEVALIER-JABET writes:
> Hello,
>
> I would like to know if interfacing FORTRAN with OCAML is possible(OCAML
> calling FORTRAN)
One issue that comes up if you are running on a 32-bit RISC machine is
alignment of doubles (8-byte floats): if you link against code which
has been compiled to assume that they are all 8-byte aligned, and use
it directly on ocaml float arrays, you get bus errors because ocaml
(on 32-bit machines) only aligns to 4-byte boundaries. I have a patch
for ocaml which makes it align doubles on 8-byte boundaries.
prev parent reply other threads:[~1999-09-02 18:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-30 12:54 karine CHEVALIER-JABET
1999-08-30 19:25 ` Xavier Leroy
[not found] ` <37CA99E6.F6616950@cea.fr>
1999-08-31 7:27 ` Patrick Goldbronn - SYSCO
1999-09-01 14:24 ` William Chesters [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=199909011424.PAA03347@toy.william.bogus \
--to=williamc@dai.ed.ac.uk \
--cc=caml-list@inria.fr \
--cc=jabet@baobab1.cad.cea.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