Hi,
Eugene Rosenzweig wrote:
However the code size would grow dramatically, for every java class there
would be an executable cache which would probably more than double the
effective size of the class takes up on disk.
And there is another reason for not doing this. Here is a snapshot of:
http:
It is certainly an enticing idea. JIT compilation offers even more code
optimisation than conventional pre-compilation so it would be quite
interesting what would happen if someone did write a jvm with jit and an
executable caching scheme. The jvm would jit-compile the code and save the
results to
