JDK-8300654 : Remove JVMFlag::flag_error_str as it is unused
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 21
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2023-01-19
  • Updated: 2023-03-09
  • Resolved: 2023-03-06
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 21
21 b13Fixed
Related Reports
Relates :  
JDK-8079408 - Improve class loading log (with unified logging)
Description
What it says in the summary.
Comments
Changeset: 8e201452 Author: Afshin Zafari <Afshin.zafari@oracle.com> Committer: Frederic Parain <fparain@openjdk.org> Date: 2023-03-06 12:46:18 +0000 URL: https://git.openjdk.org/jdk/commit/8e2014527ead67ce33627a49223b8269a94f3102
06-03-2023
This function has been unused since JDK-8079408 was fixed. I find it somewhat strange that this had such little use. It calls into question the whole Flag error code mechanism if we never even report any such errors via logging. Update: I see now that print_flag_error_message_if_needed in writeableFlags.cpp basically replaced the need to map the flag errors directly to strings.
20-02-2023
A pull request was submitted for review. URL: https://git.openjdk.org/jdk/pull/12636 Date: 2023-02-18 15:35:35 +0000
18-02-2023