On 8/16/06, Mikhail Fursov <[EMAIL PROTECTED]> wrote:
On 8/16/06, Xiao-Feng Li <[EMAIL PROTECTED]> wrote:
>
>
> > AFAIU it's enough to annotate JNI method with calling convention
> details
> > and to support it in JIT and VM. So I see no difference in
> implementation
> > with helper inlining here. Just an extension or another version of
> helper
> > inlining mechanism.
> > Am I missing something about JNI support?
>
> Yes, I guess you were missing something. ;-)
> The service routine inlining is to attack the performance issue
> brought when Java code calls into VM native services. If the JNI is
> not a problem, this Java inlining can be not very interesting.
So why can't we optimize native (JNI) calls from Java code using annotations
similar to those used to annotate helper's slow call above?
Once developer annotates native call with information about it's sideffects
we can optimize the call and reduce JNI overhead.
?
This is off-topic now. :-) But one (crazy) idea is to compile the
native code with JVM compiler as well so that both Java and native
code can use same IR.
Thanks,
xiaofeng
---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
