> 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.
Interesting, I'd think it's the other way around (in a static language anyway): A JIT can't do anything for certain, but it can do a whole lot of stuff optimistically and under the right conditions (growing impressively by each release of HotSpot) come out with a winning hand. > 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. Not necessarily, I could be wrong or this could be another definition thing! Even if code is emitted to call-site, in a language where classes can be rewritten constantly and arbitrary, there needs to be some "dirty" flag housekeeping no? -- 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.
