caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Fabrice Le Fessant <fabrice.le_fessant@inria.fr>
To: Alain Frisch <frisch@clipper.ens.fr>
Cc: OCAML <caml-list@inria.fr>
Subject: Re: JIT-compilation for OCaml?
Date: Thu, 4 Jan 2001 09:37:28 +0100 (CET)	[thread overview]
Message-ID: <14932.13896.248239.656450@cremant.inria.fr> (raw)
In-Reply-To: <Pine.GSO.4.04.10101031245050.12884-100000@clipper.ens.fr>


> Hacking ocamlrun to produce native code simply by expanding
> each opcode from the abstract machine seems fairly easy. Some
> optimizations are lost.

This has already been done by Piumarta & Riccardi (PLDI'98 ?) on the
ocaml system, version 2.04 I think.

> Another idea would be to make the compiler outputs the "lambda"
> intermediate code (shared between ocamlc and ocamlopt) and distribute
> it,

The lambda code is not exactly the same for both bytecode and native
code. This is however not a really big problem. It would probably be a
good solution, since using both dynamic linking and ocamlopt, we can
generate assembler files and then load them dynamically ...

> , maybe with some modification to prevent reverse engineering.

Don't understand what you want. Reverse engineering is always
possible ... 

> For instance, it is possible to watch conditionnal jumps and
> reorganize the code so that the most taken branches don't need any
> jump.

This has nothing to do with JIT. Using profiling information can also
be done for statically compiled programs, by recompiling them with
this information. (this is already done by many compilers).

- Fabrice



  reply	other threads:[~2001-01-04 13:32 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-02 16:07 Markus Mottl
2001-01-02 18:16 ` Mattias Waldau
2001-01-02 19:30   ` Markus Mottl
2001-01-03 12:15     ` Alain Frisch
2001-01-04  8:37       ` Fabrice Le Fessant [this message]
2001-01-04  9:04         ` Alain Frisch
2001-01-03 13:23     ` Mattias Waldau
2001-01-03 14:25       ` Markus Mottl
2001-01-03 14:40       ` STARYNKEVITCH Basile
2001-01-03 15:51     ` John Max Skaller
2001-01-03 17:50       ` Markus Mottl
2001-01-05  0:30         ` Michael Hicks
2001-01-08  9:59           ` Xavier Leroy
2001-01-09  6:40         ` John Max Skaller
2001-01-03 17:49     ` Joseph R. Kiniry
2001-01-03 18:19       ` Markus Mottl
2001-01-03 18:38         ` Joseph R. Kiniry
2001-01-03 18:58           ` Markus Mottl
2001-01-03 19:06             ` Joseph R. Kiniry
2001-01-04 22:32               ` Jonathan Coupe
2001-01-07  0:16                 ` Chris Hecker
2001-01-05 12:52               ` Sven LUTHER
2001-01-05 20:08                 ` Joseph R. Kiniry
2001-01-09  7:14             ` John Max Skaller
2001-01-09  6:50         ` John Max Skaller
2001-01-05 12:39   ` Sven LUTHER
2001-01-05  5:48 ` Vitaly Lugovsky
2001-01-03 15:24 Jerry Jackson
2001-01-04 14:12 ` Alan Schmitt
2001-01-09 17:09 Dave Berry
2001-01-11  6:38 ` John Max Skaller
2001-01-09 17:18 Dave Berry
2001-01-11  7:00 ` John Max Skaller
2001-01-11 10:01   ` Alain Frisch
2001-01-12  7:55     ` John Max Skaller
2001-01-11 12:45 Dave Berry
2001-01-12  8:23 ` John Max Skaller

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=14932.13896.248239.656450@cremant.inria.fr \
    --to=fabrice.le_fessant@inria.fr \
    --cc=caml-list@inria.fr \
    --cc=frisch@clipper.ens.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;
as well as URLs for NNTP newsgroup(s).