Instrumenting call sites.

[John Rose]

On Nov 29, 2012, at 12:40 PM, Krystal Mo wrote:

> Second, even if invokedynamic had a type profile, by default it'd only 
> keep track of 2 receiver types, which is not enough for Duncan's case.

Adding such a type profile is long-standing "fixme".  Given common usage patterns, it is probably a good idea to profile the first argument (if it is in fact a reference).

See the following comment in the x86 code for TemplateTable::invokedynamic:
    // %%% should make a type profile for any invokedynamic that takes a ref argument

Anybody want to give it a try?  It's not trivial, but reasonably straightforward given the parallel code for invokespecial, etc.

— John
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.openjdk.java.net/pipermail/mlvm-dev/attachments/20121129/1345572a/attachment.html