Re: forth and virtual memory

Anton Ertl <anton@[EMAIL PROTECTED]
> wrote:

> Another Java myth I have read is that the JIT results in faster code
> than possible with static compilation, because:

> 1) It knows exactly which CPU it is compiling for, whereas a static
> compiler typically generates code that runs on all CPUs and does not
> run too badly on any of them (and maybe even optimized for a different
> one than you have).

> 2) It knows how the program is used at run-time and can optimize for
> that usage, and adapt to changing usage patterns.

> Yet, these advantages do not seem to outweigh the overheads of JIT
> ompilation.  AFAIK Andrew Haley is still working on static Java
> compilation.

I am, but I don't think that these really are myths.  There's no doubt
in my mind that run-time optimizations can be a spectacular win.  It's
hard to compare, because programming styles are so different with Java
and languages that don't usually use GC and aren't type-safe, for
example C++.

Andrew.