Browse thread
Re: [Caml-list] avoiding native call from bytecode issue via dynamic linking
-
Rolf Wester
- Fabrice Le Fessant
[
Home
]
[ Index:
by date
|
by threads
]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
| Date: | -- (:) |
| From: | Fabrice Le Fessant <fabrice.le_fessant@i...> |
| Subject: | Re: [Caml-list] avoiding native call from bytecode issue via dynamic linking |
> 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