Initialization test

Alexandre Oliva oliva at
Thu Oct 29 08:07:21 PST 1998

Godmar Back <gback at> writes:

> Clearly, compiled code takes a hit here (gcj, for instance, always
> puts a call to the static class initializer before any static
> access).  Kaffe inserts a softcall_initialise_class if needed.

I was wondering...  If softcall_initialise_class were given a
reference to the method that is calling it, it could re-JIT-compile
that method, so that, in this recompilation, the call to
initialise_class would not be included.  It might represent a big
performance gain in a long-running application.

The re-compilation could be started in background, in a daemon thread
or such...

Alexandre Oliva
mailto:oliva at mailto:oliva at mailto:aoliva at
Universidade Estadual de Campinas, SP, Brasil

More information about the kaffe mailing list