crazy idea: gcj as a caching jit?

[Adam Megacz <gcj at lists dot megacz dot com>]

Had an idea today...

With Bryce's indirect-invoke patches, you can actually use gcj as a
caching JIT (like Microsoft's .NOT) -- hack interpret.cc to pass the
bytecodes through gcj, produce com.yourdomain.yourclass.so, dlopen()
it, and cache the .so it somewhere with an md5 of the original .class
file (to detect if newer versions of the class have arrived and need
to be recompiled).

Yet another reason I'm keen on porting gcj to more platforms -- gcc
targets a *ton* of platforms, many of which don't have
JITs. Leveraging gcc's backend makes porting gcj an easy way to get a
JIT for platforms that don't have HotSpot.

  - a