Moving the _vtable_len into Klass
john.r.rose at oracle.com
Fri Dec 18 10:33:37 UTC 2015
On Dec 17, 2015, at 6:29 AM, Mikael Gerdin <mikael.gerdin at oracle.com> wrote:
> My current plan is to first modify the vtable_length_offset accessor to return a byte offset (which is what it's translated to by all callers).
> Then I'll tackle moving the _vtable_len field to Klass.
> Finally I'll try to consolidate the vtable related methods to Klass, where they belong.
> The vtable_start_offset is a slightly more difficult beast since it's more often used in wordSize scaled calculations, my current idea is to leave it alone for now.
> Does that sound like a good plan?
Sure, that's fine. It might be slightly better if you could make vtable_start_offset also be unscaled, but (as I said) that's more of a long-term goal, to move towards unscaled offset calculations.
More information about the hotspot-dev