On Fri, 5 Jul 2024 16:54:41 GMT, Justin Lu wrote:
> Following up on my previous comment regarding the _untrue wording_.
>
> I no longer think we can just split the implementation and specification
> portion of this PR into two issues, since if we backport the implementation
> only, the specifi
On Mon, 8 Jul 2024 02:32:17 GMT, lingjun-cg wrote:
>> ### Performance regression of DecimalFormat.format
>> From the output of perf, we can see the hottest regions contain atomic
>> instructions. But when run with JDK 11, there is no such problem. The
>> reason is the removed biased locking.
> ### Performance regression of DecimalFormat.format
> From the output of perf, we can see the hottest regions contain atomic
> instructions. But when run with JDK 11, there is no such problem. The reason
> is the removed biased locking.
> The DecimalFormat uses StringBuffer everywhere, and St
Make well-behaved implementation expectations of Object.{toString, hashCode}
explicit.
-
Commit messages:
- JDK-8335637: Add explicit well-behaved expectations to Object.{toString,
hashCode}
Changes: https://git.openjdk.org/jdk/pull/20063/files
Webrev: https://webrevs.openjdk.or
