P4
This is a continuation of
https://bugs.openjdk.java.net/browse/JDK-6736490
https://bugs.openjdk.java.net/browse/JDK-8035284
https://bugs.openjdk.java.net/browse/JDK-8145680
https://bugs.openjdk.java.net/browse/JDK-8251548
As Doug Lea claims in http://cs.oswego.edu/pipermail/concurrency-interest/2015-December/014770.html
"there is never any reason to explicitly initialize fields to 0/0.0/false/null"
Explicit initialization of volatile variable to a value the same as the default implicit initialized value results in an unnecessary store and membar operation.
https://bugs.openjdk.java.net/browse/JDK-6736490
https://bugs.openjdk.java.net/browse/JDK-8035284
https://bugs.openjdk.java.net/browse/JDK-8145680
https://bugs.openjdk.java.net/browse/JDK-8251548
As Doug Lea claims in http://cs.oswego.edu/pipermail/concurrency-interest/2015-December/014770.html
"there is never any reason to explicitly initialize fields to 0/0.0/false/null"
Explicit initialization of volatile variable to a value the same as the default implicit initialized value results in an unnecessary store and membar operation.
