RFR: 8181085: Race condition in method resolution may produce spurious NullPointerException

Andrew Haley aph at redhat.com
Tue May 30 09:59:21 UTC 2017


Just to be clear on my position: we want to constrain the compiler as
little as we can, while maintaining correctness.  x86 OrderAccess was
incorrect, so compiler barriers had to be added.  Where volatile is
sufficient we should use that today, but bear in mind that racy
accesses are now undefined behaviour in C++.

Andrew.


More information about the jdk10-dev mailing list