Version française
Home     About     Download     Resources     Contact us    
Browse thread
[Caml-list] Co-existence of byterun and asmrun impossible?
[ Home ] [ Index: by date | by threads ]
[ Search: ]

[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
Date: -- (:)
From: Nuutti Kotivuori <naked+caml@n...>
Subject: [Caml-list] Co-existence of byterun and asmrun impossible?
It took me a while to realize this - and I just wish to make sure that
I haven't misunderstood anything.

The byterun and asmrun parts cannot co-exist in a single executable?

It's possible to *compile* native code with a compiler in bytecode,
and to compile bytecode with a compiler in native code, but it is not
possible to *run* bytecode with an executable that isn't bytecode? 
That is, a native compiled version of ocamlrun could never exist -
eg. no ocamlrun.opt nor ocaml.opt (native toplevel)?

I never thought of this before - it seems rather natural, but it's
still a bit of a bummer. This means that if a program needs to
interpret bytecode, no ocaml code in it may be natively compiled -
which in turn means any performance sensitive code needs to be hand
written in C.

Well, I'm not counting in the possibility of dynamically loading both
camlrun and asmrun and calling them directly - but even still they
couldn't share values and there would be two separate garbage
collectors.

I expect that this is a rather fundamental restriction and not easily
removed?

Bummed out,
-- Naked

-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners