From: Alan Schmitt <alan.schmitt@inria.fr>
To: OCAML <caml-list@inria.fr>
Subject: Re: JIT-compilation for OCaml?
Date: Thu, 4 Jan 2001 15:12:56 +0100 [thread overview]
Message-ID: <20010104151256.B13161@alan-schm1p> (raw)
In-Reply-To: <03E742431696D311BD1B00062938251704C4C6AD@cpex1.channelpoint.com>; from jrj@channelpoint.com on Wed, Jan 03, 2001 at 08:24:53AM -0700
This reminds me of slim binaries and runtime optimizations ...
(see http://caesar.ics.uci.edu/oberon/research.html#SlimBinaries )
I noticed something funny there: the PhD student who was working on
dynamic optimizations is now working for Transmeta. What a coincidence
;-)
Alan Schmitt
>[JRJ] There are many other sorts of optimizations that can be done by
>compiling at runtime. A simple case is that processor-specific instructions
>can be generated instead of generic ones (e.g. Pentium III instructions
>rather than generic 486). A more interesting example is used by Sun's
>current JIT compiler... Aggressive inlining and direct dispatch are done
>for all sorts of method calls (that could potentially be overloaded). If a
>class is later loaded that extends one of the inlined or directly called
>methods, the JIT compiler goes back and "unoptimizes" the code it had
>previously optimized!
--
The hacker: someone who figured things out and made something cool happen.
next prev parent reply other threads:[~2001-01-04 20:19 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-03 15:24 Jerry Jackson
2001-01-04 14:12 ` Alan Schmitt [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-11 12:45 Dave Berry
2001-01-12 8:23 ` 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-09 17:09 Dave Berry
2001-01-11 6:38 ` John Max Skaller
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
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
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=20010104151256.B13161@alan-schm1p \
--to=alan.schmitt@inria.fr \
--cc=caml-list@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).