[concurrency-interest] Is Reference.reachabilityFence() needed in Reference constructor? (original) (raw)
Andrew Haley aph at redhat.com
Wed Oct 21 15:53:38 UTC 2015
- Previous message: [concurrency-interest] Is Reference.reachabilityFence() needed in Reference constructor?
- Next message: [concurrency-interest] Is Reference.reachabilityFence() needed in Reference constructor?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 10/21/2015 04:44 PM, Aleksey Shipilev wrote:
Of course, this does not tell another (scary) part of the story, what if the Reference itself is not discovered as strong ref by GC, e.g. when it isn't published on heap, or scalarized by compiler, etc. reachabilityFence, as currently implemented, extends the "liveness" scope of the local variable, but does not convey anything special to the GC/runtime otherwise.
If the Reference itself is not reachable from a strong root then the Reference is dead so we don't care what happens to it. But if the Reference is put on a reachable ReferenceQueue, then it's fine.
Andrew.
- Previous message: [concurrency-interest] Is Reference.reachabilityFence() needed in Reference constructor?
- Next message: [concurrency-interest] Is Reference.reachabilityFence() needed in Reference constructor?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]