From: Vitaly Lugovsky <vsl@ontil.ihep.su>
To: caml-list@inria.fr
Subject: JIT compilation
Date: Tue, 30 Jan 2001 15:01:06 +0300 (MSK) [thread overview]
Message-ID: <Pine.LNX.4.10.10101301453030.1968-100000@ontil.ihep.su> (raw)
I just found a lot of troubles with JIT compilation:
some instructions (APPLY*, APPTERM*, RETURN, RAISE, GRAB) takes
branching address from stack, so, we can't determine its transition to
compiled address at compile time, and, so, we don't know exactly "entry
points", which can't be optimized out. We need some additional information
from compilator along with bytecode. Is it possible to produce a kind of
branching tables at a bytecode compilation time? Without this stuff we
just can produce flat, unoptimized native code, with transition table
for all possible addresses (it will be BIG and SLOW)...
--
V.S.Lugovsky aka Mauhuur (http://ontil.ihep.su/~vsl) (UIN=45482254)
reply other threads:[~2001-01-31 11:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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.LNX.4.10.10101301453030.1968-100000@ontil.ihep.su \
--to=vsl@ontil.ihep.su \
--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).