CAS in load barrier self-healing

[Florian Weimer]

How performance-sensitive is this code path?  I wonder if this could be
a regular store if the field is final, final fields are trusted, and the
class has only constructors that write to each final field once.

In this case, the data race is benign, I think: Outside the barrier, the
mutator may write a non-null pointer, but then the previous pointer must
have been null.  Several Two mutator threads may update the same field
in the barrier, but new object address is the same on all threads.

Thanks,
Florian