Hi,

profiling initializers in java.lang.invoke shows we're still doing various things during class initialization which could be done lazily or not at all. The proposed patch
reduce bytecode executed, memory churn and retained heap footprint when
initializing java.lang.invoke:

Webrev: http://cr.openjdk.java.net/~redestad/8178384/jdk.01/
Bug: https://bugs.openjdk.java.net/browse/JDK-8178384

Testing: java.lang.invoke jtreg tests, sanity performance testing

Thanks!

/Claes

Reply via email to