8179527: Ineffective use of volatile hurts performance of Charset.atBugLevel()
claes.redestad at oracle.com
Tue Jun 27 07:36:20 UTC 2017
On 2017-06-27 09:01, Alan Bateman wrote:
> It might be better if we can just remove the test from
> Charset.checkName as I think that dates back to an incompatible change
> going from JDK 1.4 to JDK 5 that should no longer be a concern.
The check of Charset.atBugLevel in checkName should no longer happen for
the majority of situations, as that test is now only done if the charset
name is "" (see https://bugs.openjdk.java.net/browse/JDK-8174831), since
what differs between 1.4 and 1.5 was apparently whether or not the empty
string was to be accepted as a valid Charset...
So yes, if we can get rid of the test altogether, we'll be even better off!
More information about the nio-dev