From: Alain Frisch <frisch@clipper.ens.fr>
To: Fabrice Le Fessant <fabrice.le_fessant@inria.fr>
Cc: OCAML <caml-list@inria.fr>
Subject: Re: JIT-compilation for OCaml?
Date: Thu, 4 Jan 2001 10:04:34 +0100 (MET) [thread overview]
Message-ID: <Pine.GSO.4.04.10101040950480.21705-100000@clipper.ens.fr> (raw)
In-Reply-To: <14932.13896.248239.656450@cremant.inria.fr>
On Thu, 4 Jan 2001, Fabrice Le Fessant wrote:
> > , maybe with some modification to prevent reverse engineering.
>
> Don't understand what you want. Reverse engineering is always
> possible ...
I meant: making it more laborious. For instance by changing the name of
identifiers or the structure of the code. I know that Java bytecode has
been blamed for allowing straightforward reverse engineering by
recognizing standard patterns associated to constructions in the source.
For OCaml, the lambda representation may be already far enough from
the source code.
> > 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).
My point, precisely. If the JIT can't make the code run faster than
a static bytecode-to-nativecode converter, that is, if it doesn't use
any profiling information, I don't see how it is useful.
--
Alain
next prev parent reply other threads:[~2001-01-04 13:33 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
2001-01-04 9:04 ` Alain Frisch [this message]
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=Pine.GSO.4.04.10101040950480.21705-100000@clipper.ens.fr \
--to=frisch@clipper.ens.fr \
--cc=caml-list@inria.fr \
--cc=fabrice.le_fessant@inria.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).