From: Fabrice Le Fessant <fabrice.le_fessant@inria.fr>
To: "Rolf Wester" <rolf.wester@ilt.fhg.de>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] avoiding native call from bytecode issue via dynamic linking
Date: Mon, 12 Nov 2001 08:58:38 +0100 (CET) [thread overview]
Message-ID: <15343.33070.25617.279577@lachesis.inria.fr> (raw)
In-Reply-To: <3BEC0E53.6797.26E241B7@localhost>
> Jeff Henrikson wrote:
> > Has anybody considered sidestepping the native/bytecode compatablity
> > issue in favor of an all native toplevel? That is, one which takes an
> > expression, compiles it to native code, and loads it back in to code
> > space? For example, write it out to a shared lib, either one for each
> > expression (or more likely for efficiency) one for some reasonably sized
> > history of expressions. Then dlopen and dlsym the symbols into place.
> >
> It would be great to have a toplevel that compiles to native code. If this
> would only be possible under UNIX I would immediately change from NT to
> Linux (what I probably should do anyway). Native code compilation in the
> toplevel was one of the reasons to consider to use Lisp.
I've started working on a very simple JIT for Ocaml. It is not working
yet (I'm a busy programmer) , but I have a module which ouputs native
i386 code in memory that might be useful, if someone wants to try to
plug it into the backend of the native code compiler ...
- Fabrice
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
next prev parent reply other threads:[~2001-11-12 8:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-09 15:11 Rolf Wester
2001-11-12 7:58 ` Fabrice Le Fessant [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-09-25 21:22 [Caml-list] calling native from bytecode (was RE: a regular expression library) Chris Hecker
2001-11-09 15:09 ` [Caml-list] avoiding native call from bytecode issue via dynamic linking Jeff Henrikson
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=15343.33070.25617.279577@lachesis.inria.fr \
--to=fabrice.le_fessant@inria.fr \
--cc=caml-list@inria.fr \
--cc=rolf.wester@ilt.fhg.de \
/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).