Re: JIT optimization framework (was: Re: [Sablevm-user] bug report...)

[Andrew P. <apu...@ac...>]

"Etienne M. Gagnon" wrote:
> Soot has not only scalar optimizations, but also OO analyses/
> transformations.  

Soot does indeed sound like a good starting point. I'll read the
available papers -- and code, eventually -- with an eye toward
determining how expensive (in terms of time) the current set of
analyses and transformations are. 

I was going to put together something as simple and lightweight
as possible, but considering an aggressively optimizing JIT is
best applied selectively, there may be some wiggle room. Hmm.
I'm getting ahead of myself. Soot (or a subset) may well be
appropriate.

> You would think that Sun's HotSpot would not get any gain
> from such a static optimizer, but you would be wrong (as we have
> unexpectedly discovered); statically optimized class files were
> faster on many vms and many platforms (Linux,WinNT,...). 

I truly don't know anything about HotSpot, but I know people who
do, and I commonly hear it is constructed of rubber bands and
matchsticks. Those same folks claim IBM's JVM is much better.


Andrew Purtell
from home -- apu...@ac...