It was Class.h actually... :)

I'm afraid if I do that, those supporting JITs will come after me, and I
won't write any more to this list.

P.S. It might be not that bad from someones POV, but I would prefer staying
alive...

On 11/3/06, Geir Magnusson Jr. <[EMAIL PROTECTED]> wrote:



Pavel Pervov wrote:
> Hello, community,
>
> Working through DRLVM sources I (once again) looked at organization of
> jitrino code.
>
> Actually, there are two JITs hidden inside "jitrino": JET and OPT.
>
> As far as I may observe - these two are code-independent from each
other.
>
> JIT-guys, could you comment?
>
> If I'm right here I would vote for moving them to top level of
> drlvm/trunk/vm directory to clearly indicate we have two JITs in DRLVM.
>

That's cool, and helps show that the jit is pluggable.  But lets not go
through the same saga as the jni.h cleanup :)

before you submit a big patch, lets sketch it out, and maybe it's
something someone can "just do".

geir




--
Pavel Pervov,
Intel Enterprise Solutions Software Division

Reply via email to