GC interface update
shade at redhat.com
Thu Apr 20 10:05:25 UTC 2017
On 04/20/2017 09:37 AM, Kirk Pepperdine wrote:
>> Good stuff. However, one thing I'm not quite comfortable with is the
>> introduction of the GC class (and its sub classes). I don't quite see the
>> purpose of this interface split-up between GC and CollectedHeap. I view
>> CollectedHeap as _the_ interface (but yes, it needs some love), and as a
>> result I think the the functions you've exposed in the GC class actually
>> belongs in CollectedHeap.
> I thought the name CollectedHeap implied the state of the heap after the
> collector has completed. What is the intent of CollectedHeap?
No, CollectedHeap is the actual current GC interface. This is the entry point to
GC as far as the rest of runtime is concerned, see e.g. CollectedHeap*
Universe::create_heap(), etc. Implementing CollectedHeap, CollectorPolicy, and
BarrierSet are the bare minimum required for GC implementation today. 
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 819 bytes
Desc: OpenPGP digital signature
More information about the hotspot-gc-dev