GC interface update
kirk at kodewerk.com
Wed Apr 12 19:54:07 UTC 2017
> On Apr 12, 2017, at 9:10 PM, Roman Kennke <rkennke at redhat.com> wrote:
> Am 12.04.2017 um 21:02 schrieb Christian Thalinger:
>> Two or three JavaOnes ago Jon Masa (where is he anyway? ;-)
> I think he retired?
He retired just after JavaONE.
>> 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?
> That's a tricky one.
You could inject the barrier rules into the compiler? The compiler would also need an interface for this to work.
> I'm thinking to have sub-interfaces, e.g. C2GCSupport and C1GCSupport
> provided by the GC interface main class. Those guys must know about both
> their respective compiler interfaces (e.g. Node, GraphKit, etc) and
> their GC. The compiler would then simply call something like
> GC::gc()->c1_support()->pre_barrier(...) instead of switching on the
> barrier-type and assuming knowledge about the particular GCs. Same goes
> for jvmci I think, but haven't put much thought on it yet. In fact, it
> would be helpful to know what you, as a compiler guy, would ideally use
> as GC interface. ?
More information about the hotspot-gc-dev