JDK-8361086 : JVMCIGlobals::check_jvmci_flags_are_consistent has incorrect format string
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 15
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2025-06-30
  • Updated: 2025-09-12
  • Resolved: 2025-07-02
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.
JDK 26
26 b05Fixed
Related Reports
Blocks :  
JDK-8198918 - jio_snprintf and friends are not checked by -Wformat
Causes :  
JDK-8241232 - -XX:+BootstrapJVMCI is not compatible with TieredStopAtLevel < CompLevel_full_optimization
Description
JVMCIGlobals::check_jvmci_flags_are_consistent uses jio_fprintf to print a warning message including the value of TieredStopAtLevel. The type of that option is intx, but "%d" is used to print it, which is incorrect for 64bit platforms.
Comments
Changeset: c6448dc3 Branch: master Author: Kim Barrett <kbarrett@openjdk.org> Date: 2025-07-02 00:28:24 +0000 URL: https://git.openjdk.org/jdk/commit/c6448dc3afb1da9d93bb94804aa1971a650b91b7
02-07-2025
ILW = MLM = P4
01-07-2025
> This begs the question of why TieredStopAtLevel is of type intx rather than int FTR, this is now tracked by JDK-8361173.
01-07-2025
A pull request was submitted for review. Branch: master URL: https://git.openjdk.org/jdk/pull/26051 Date: 2025-06-30 16:14:08 +0000
30-06-2025
This begs the question of why TieredStopAtLevel is of type intx rather than int, since it's value is restricted to the range [0-4]. For that matter, there are a lot of other options in compiler_globals.hpp that that seem to be inappropriately typed as intx.
30-06-2025