RFR: Factor out keep-alive barrier

[Roman Kennke]

Am 6. September 2017 16:35:39 MESZ schrieb Aleksey Shipilev <shade at redhat.com>:
>On 09/06/2017 03:58 PM, Roman Kennke wrote:
>> OK, I will put it back in. It will all change with the GC interface
>anyway...
>> 
>>> *) ShenandoahSATBBarrier should be handled in
>>> ShenandoahBarrierSet::keep_alive_barrier?
>
>Seems fine with me. ShenandoahSATBBarrier can be just renamed for this,
>right?

No no :-) We still do have actual SATB barriers on oop stores. This here is about keeping objects alive for various reasons not related to SATB, e.g. on Reference.get()

Roman


-- 
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.