On 8/16/06, Xiao-Feng Li <[EMAIL PROTECTED]> wrote:
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.
Actually, its not really off-topic. It is not crazy. ECMA CLI does something very similar. The unspoken challenge is to extend the Java bytecode set so that it can express arbitrary unsafe source code. In a sense, the discussion about inlining JNI and native code, etc is really a discussion about which specific features of unsafe code the JIT should comprehend. Right now, vmmagic does a good job of providing "C" style address arithmetic and "void *" pointers. Its a start but not complete. Given the above, perhaps it makes sense to let the JIT developers do opportunistic inlining of assembly code snippets of DRLVM where it make sense. That is, not design a complex protocol for the JIT to discover what can be inlined. Simply hardcode to the situation. Leave the real optimizing inlining to situations where the helper is indeed expressed as standard Java source code.
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]
-- Weldon Washburn Intel Middleware Products Division --------------------------------------------------------------------- Terms of use : http://incubator.apache.org/harmony/mailing.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
