Since Klass is now responsible for maintaining the offsets and length of the embedded vtable it makes sense to move all code related to the Java vtables to Klass.
This also allows us to remove a few unsafe casts where an ArrayKlass was cast to an InstanceKlass just to get at the methods_at_vtable().
This also allows us to remove a few unsafe casts where an ArrayKlass was cast to an InstanceKlass just to get at the methods_at_vtable().
- relates to
-
JDK-8148945 JDK-8148481: Devirtualize Klass::vtable breaks Zero build
-
- Resolved
-