Request for review (L): 7087838: JSR 292: add throttling logic for optimistic call site optimizations

[Mark Roos]

Thanks but I do have a few questions that are not being answered.


First is the decision by the compiler to not  jit a callsite reversible 
without restarting
the program?  I am very worried that the mere act of invalidating 
callsites to force them
to use new code (something that happens a lot in Smalltalk) will send my 
app to interpreter 
purgatory.  I really need a way to invalidate the sites ( which right now 
can only be done
via a setTarget ( I think) without forcing them to not be jitted.

Second
Christian mentioned:  As Remi mentioned we need throttling like this
What is the use case that is being fixed by this?  It seems that I can fix 
it on my end by watching
the call depth ( which I do ) so why does the compiler need to do it for 
me? 

Third.  I am sure there is a very cool vTable lookup in the low level 
code.  How can I get to 
that?  I am concerned that writing a high level vTable will be slow.  At 
least slower that
a  few GWTs

Thanks

mark
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.openjdk.java.net/pipermail/mlvm-dev/attachments/20110920/f2fb96d1/attachment.html