[9] RFR (S) 8147978: Remove Method::_method_data for C1

John Rose john.r.rose at oracle.com
Fri Feb 26 01:14:29 UTC 2016

On Feb 3, 2016, at 11:20 PM, Chris Plummer <chris.plummer at oracle.com> wrote:
> Please review the following for removing Method::_method_data when only supporting C1 (or more specifically, when not supporting C2 or JVMCI). This will help reduce dynamic footprint usage for the minimal VM.

Even with C2 we could save footprint if we could merge the _method_data and _method_counters field.

Even on C1, with this change, we could save more footprint if we could make the _method_counters field a tagged union between a short count and the full method counters field, allocated lazily after (say) 10 iterations of a method.

The tracking bug for this is https://bugs.openjdk.java.net/browse/JDK-8013169 <https://bugs.openjdk.java.net/browse/JDK-8013169>

I just added a comment explaining the lazy allocation idea.

Any takers?

— John
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openjdk.java.net/pipermail/hotspot-compiler-dev/attachments/20160225/3827ac9b/attachment.html>

More information about the hotspot-compiler-dev mailing list