The information a JIT sees is correct, whereas the information a source compiler sees could be made incorrect easily by having a different classpath at runtime. Thus there's more a JIT can safely do.
> That's mostly a definition issue isn't it? You still can't inline > statically, but you CAN remember the slot in the VTABLE which was used > last time and jump directly there if not marked dirty. I thought it would actually inline the thing, as in copying the machine code into the calling method, but it sounds like you know more about this than I do. -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
