<html>
<body>
<font size=3>At 12:48 PM 1/10/2005, Eli Barzilay <eli@barzilay.org>
wrote:<br>
<blockquote type=cite class=cite cite="">On Jan 10, Blake McBride
wrote:<br>
> Is there any plan to improve mzc? As you are all probably
aware,<br>
> the output of mzc offers little optimization when compared to<br>
> chicken or bigloo. MzScheme is a great development platform
and has<br>
> a lot of really nice features. It would be nice to be able
to<br>
> compile it to a form more comparable to C programs as does
Chicken<br>
> and Bigloo.<br><br>
The current plan is to work on a more proper JIT compiler, instead
of<br>
going through C. How fast will that be compared to other compiler
is<br>
a question, but it will most likely be an improvement of the
current<br>
state (and hopefully an improvement over mzc-compiled code
too).<br><br>
-- <br>
((lambda (x) (x
x)) (lambda (x) (x
x))) Eli
Barzilay:</font></blockquote><br><br>
Why go through all the work of writing a JIT compiler when they are<br>
entirely CPU specific? Doesn't it make more sense to spend all
that<br>
effort to generate portable optimized C? Who cares how fast the
interpreter<br>
works (within reason) so long as a fast compiler is available?
Portability<br>
is an important issue.<br><br>
I know JIT compilers are in vogue but an optimizing compiler through C
makes <br>
much more sense.<br><br>
Thanks.<br><br>
Blake McBride<br>
</body>
</html>