JDK-8364025 : MinMaxVector clipping range benchmark highestInt/Long can overflow
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 25
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • Submitted: 2025-07-24
  • Updated: 2025-07-25
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
tbdUnresolved
Related Reports
Causes :  
JDK-8307513 - C2: intrinsify Math.max(long,long) and Math.min(long,long)
Description
I discovered this while working on JDK-8351409.

The clipping range method in the MinMaxVector JMH benchmark has an overflow issue when calculating `highestInt` and `highestLong`. If they overflow, the range parameter won't work as expected and therefore the branch taken/not-taken expectations won't be matched. When this happens, the results of the benchmark cannot be trusted.
Comments
ILW = MLH = P4
25-07-2025