From: Fabrice Le Fessant <fabrice.le_fessant@inria.fr>
To: Vitaly Lugovsky <vsl@ontil.ihep.su>
Cc: caml-list@inria.fr
Subject: Re: Dynamic loading. Again.
Date: Wed, 29 Nov 2000 17:42:10 +0100 (CET) [thread overview]
Message-ID: <14885.12770.825697.215308@cremant.inria.fr> (raw)
In-Reply-To: <Pine.LNX.4.10.10011260300170.18840-100000@ontil.ihep.su>
Last year, Mark Hayden and I did some work on dynamic linking of
native code for Linux. It worked, with few modifications in the
compiler to generate relocatable code in the ELF format, but the code
was really big (something like twice the normal size) and really slow
(about twice slower). It was for ocaml 2.??, but it should probably
work with a few changes for the current version. If you want the
patch, I will try to find it in my archives. It was a few days work,
so we dit not optimize it as it should be, but it can be used as a
start point.
If you are only interested with linking some code -- not time
critical --, you can try the dynlink library which is included in the efuns
package (http://pauillac.inria.fr/efuns). It will allow you to
dynamically link BYTECODE modules inside NATIVE code programs. These
modules will be executed slower than the native code, and even slower
than the bytecode run by ocamlrun, but they will use native functions
for all functions which were included in the program, so that it would
be good to execute powerful configuration scripts, or computation
orders.
Regards,
- Fabrice
Homepage: http://pauillac.inria.fr/~lefessan
next prev parent reply other threads:[~2000-11-29 21:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-26 0:09 Vitaly Lugovsky
2000-11-28 1:27 ` John Max Skaller
2000-11-29 16:42 ` Fabrice Le Fessant [this message]
2000-11-30 7:02 ` John Max Skaller
2000-11-30 16:08 ` Fabrice Le Fessant
2000-12-01 12:59 ` John Max Skaller
2000-12-01 14:24 ` Fabrice Le Fessant
2000-12-01 16:49 ` John Max Skaller
2000-12-04 21:06 ` Gerd Stolpmann
2000-11-30 18:00 ` Chris Hecker
2000-12-01 13:34 ` John Max Skaller
2000-11-30 20:55 ` Gerd Stolpmann
2000-11-28 11:14 Ken Wakita
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=14885.12770.825697.215308@cremant.inria.fr \
--to=fabrice.le_fessant@inria.fr \
--cc=caml-list@inria.fr \
--cc=vsl@ontil.ihep.su \
/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