RFR: Here are some Thread cleanup patches

David Holmes david.holmes at oracle.com
Tue Mar 27 23:42:24 UTC 2018

Hi Martin,

On 28/03/2018 4:28 AM, Martin Buchholz wrote:
> The usual story when I change Thread.java is that I'm missing something and
> I end up reverting, so I was extra careful this time.
> 8200122: Remove unused field Thread.threadQ
> http://cr.openjdk.java.net/~martin/webrevs/jdk/Thread-threadQ/
> https://bugs.openjdk.java.net/browse/JDK-8200122

Looks fine.

> 8200123: Replace Thread.init with telescoping constructor
> http://cr.openjdk.java.net/~martin/webrevs/jdk/Thread-init/
> https://bugs.openjdk.java.net/browse/JDK-8200123

Looks fine - for some reason I thought we had a direct VM call to init() 
but we don't.

What is the effect of @stable? I'm just thinking about any possible 
impact on initialization order.


More information about the core-libs-dev mailing list