JDK-8366214 : [lworld] Use Objects.equals in HashMap and ConcurrentHashmap
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.util
  • Affected Version: repo-valhalla
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2025-08-26
  • Updated: 2025-12-10
  • Resolved: 2025-09-03
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
repo-valhallaFixed
Related Reports
Causes :  
JDK-8373466 - [world] javax.xml TransformerTest fails after change to HashMap.
Cloners :  
JDK-8373361 - Use of identity in HashMap and ConcurrentHashmap comparisons
Relates :  
JDK-8371497 - Simplify java.util.Object.equals - remove the identity comparison
Relates :  
JDK-8366043 - [lworld] (LIFE = Legacy Idiom For Equality) causes performance regressions
Description
The Legacy Idiom checking for reference equality before calling Object.equals should be replaced with calls to Objects.equals.
Replacing them in HashMap and ConcurrentHashMap, as noted in JDK-8366043, it will allow easier experiments with performance of ==.
Comments
A pull request was submitted for review. Branch: lworld URL: https://git.openjdk.org/valhalla/pull/1536 Date: 2025-08-27 19:40:28 +0000
27-08-2025