It is not javac that generates the native code, it is a AOT compiler inside the runtime that just starts to produce native code (current shared objects - .so files) at runtime. It will probably only create them once and reuses them the next time (memorization) but the JIT can override the AOT compiled code whenever it has enough metrics.
mhm, primitive generics, much more interesting 
Sounds like someone’s smoking crack…or I’m completely misunderstand this. The sane time to memorize is after interpretation/stats-gathering and all (expected) standard compilations have already occurred and re-use this memorized version at load time iff hotspot and classfile are the same. The runtime has to be able to override memorized versions…example optimistic choice is disproven (really memorized just allows bypassing)
i couldn’t follow the presenter that good.
i guess you’re talking about a cache and not aot, like ahead of. their demo compiles every path statically which generates too many classes to be any beneficial … or was that the other topic. :persecutioncomplex:
Stopped listening at “commercial feature”.
I just finished an article about the new world after sun.misc.Unsafe which includes also a short view on specialized generics. Will hopefully released begin of next week. 