[9] RFR (M): 8057967: CallSite dependency tracking scales devastatingly poorly

John Rose john.r.rose at oracle.com
Thu Apr 2 02:27:00 UTC 2015

On Apr 1, 2015, at 1:56 PM, Vladimir Ivanov <vladimir.x.ivanov at oracle.com> wrote:
> http://cr.openjdk.java.net/~vlivanov/8057967/webrev.00/hotspot/
> http://cr.openjdk.java.net/~vlivanov/8057967/webrev.00/jdk/
> https://bugs.openjdk.java.net/browse/JDK-8057967

Impressive work.

Question:  How common is state 2 (context-free CS) compared to state 3 (indy-bound CS)?

And is state 2 well tested by Box2D?

I recommend putting CONTEXT_OFFSET into CallSite, not the nested class.
For one thing, your getDeclaredField call will fail (I think) with a security manager installed.
You can load it up where TARGET_OFFSET is initialized.

I haven't looked at the JVM changes yet, and I don't understand the cleaner, yet.

Can a call site target class change as a result of LF recompiling or customization?
If so, won't that cause a risk of dropped dependencies?

— John

More information about the core-libs-dev mailing list