RFR (XXS): 8023191: OSR nmethods should be flushed to free space in CodeCache

John Rose john.r.rose at oracle.com
Thu Oct 10 09:47:54 PDT 2013

On Oct 10, 2013, at 8:34 AM, Albert Noll <albert.noll at oracle.com> wrote:

> There is one thing I do not understand in the current implementation. What is the reason
> that OSR nmethods are maintained in InstanceKlass and not in Method?
> I do not see a reason but maybe I am missing something.

The basic assumption in HotSpot before OSR is that each bytecode method has zero or one compiled versions.

With OSR, we need multiple versions (for different entry points).  Putting this in required an ad hoc data structure that had to be built on the side.

See my earlier message for where I think the "sweet spot" is:  A way to bind a specific method to zero or more versioned n-methods.

— John
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.openjdk.java.net/pipermail/hotspot-compiler-dev/attachments/20131010/77ac268c/attachment.html 

More information about the hotspot-compiler-dev mailing list