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

David Holmes david.holmes at oracle.com
Tue May 30 21:33:47 UTC 2017


<trimming>

On 30/05/2017 10:45 PM, Andrew Haley wrote:
> You have to remember where this discussion started, which was a
> proposed use of volatile to fix a bug where a barrier was needed.

No that was not the case, as has been pointed out numerous times. There 
were two bugs:

1. Incorrect placement of volatile in a declaration
2. Need to backport the compiler_barrier changes for OrderAccess.

No one suggested doing #1 in lieu of #2. We wanted #1 as well as #2.

David



More information about the jdk10-dev mailing list