GC interface update

Christian Thalinger cthalinger at twitter.com
Wed Apr 12 19:02:41 UTC 2017


Two or three JavaOnes ago Jon Masa (where is he anyway? ;-) and I discussed JVMCI and a possible GC interface.  One issue with compilers is that they need to emit different barrier code for different garbage collectors.  You mention this in the JEP.

Where are you with your thinking on this?

> On Apr 12, 2017, at 4:46 AM, Roman Kennke <rkennke at redhat.com> wrote:
> 
> I spent some more time working on the GC interface prototype and wanted
> to share it with you:
> 
> http://cr.openjdk.java.net/~rkennke/gc-interface/webrev.02/
> <http://cr.openjdk.java.net/%7Erkennke/gc-interface/webrev.02/>
> 
> Notable changes:
> 
> - It's now based on JDK10 (specifically,
> http://hg.openjdk.java.net/jdk10/hs/hotspot changeset 12853:d276073fda85)
> - I focused on better CMS isolation:
>  - Most CMS specific stuff from GenCollectedHeap now resides in
> specific subclass CMSHeap
>  - Same for CardTableModRefBSForCTRS -> CMSBarrierSet
>  - Factored everything related to always_do_update_barrier_set into CMS
> subclasses
> 
> The JEP is still in 'submitted' state. Would be good to have it moved to
> 'candidate' at least, so that it gets a number?
> 
> https://bugs.openjdk.java.net/browse/JDK-8163329
> 
> Does anybody know a good place where I could put a whole forest to
> develop this in?
> 
> As always, any feedback is welcome.
> 
> Best regards,
> Roman
> 



More information about the hotspot-gc-dev mailing list