RFR (S) 8182397: Race in field updates when creating ArrayKlasses can lead to crash

Andrew Haley aph at redhat.com
Tue Jul 25 16:47:49 UTC 2017

On 25/07/17 16:36, Erik Österlund wrote:
> Would you agree it would be beneficial to use load_acquire at least in 
> this not so hot path in the C++ code? Then we have indisputably correct 
> synchronization in the C++ code, can dodge the whole consume discussion 
> (we do what every other acquire/release pair does in hotspot - business 
> as usual), and leave the optimized case to our own JIT compilers that we 
> trust retain the data dependency. I would be happy with that.

I would too.  If acquire gets used in places where a data dependency could
be used at some point in the future, we can have this argu^H^H^H^H discussion
again.  :-)

Andrew Haley
Java Platform Lead Engineer
Red Hat UK Ltd. <https://www.redhat.com>
EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671

More information about the hotspot-dev mailing list