I was apparently mislead by things I read about Dalvik; or perhaps I assumed that "dexopt" actually compiled things to native code, rather than just aligning code, replacing field references with pointer offsets, and so on. The official word is that Dalvik was 100% interpreted up until Froyo, and post-Froyo it employs a tracing JIT to improve performance (same sort of compiler optimization as V8). I updated my post to reflect this.
I couldn't get the Channel 9 Eric Meijer video to work, but all the references I've found online about V8 seem to say that it always goes to native code before executing. The wikipedia article (http:// en.wikipedia.org/wiki/V8_(JavaScript_engine)) says: "V8 increases performance by compiling JavaScript to native machine code before executing it, rather than to a bytecode or interpreting it." - Charlie On Aug 16, 3:28 pm, Casper Bang <casper.b...@gmail.com> wrote: > > A commenter said instead Android 2.2 does mixed mode: > > That was my understanding too, from this years Google IO > talk:http://www.taranfx.com/android-internals-jit-froyo > > I also believe V8/Chrome does > mixed-mode:http://channel9.msdn.com/shows/Going+Deep/Expert-to-Expert-Erik-Meije... > > But perhaps Charles Nutter is simply ahead of all of us! :) -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to javapo...@googlegroups.com. To unsubscribe from this group, send email to javaposse+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
