JDK-8216995 : Clean up JFR command line processing
- Type: Enhancement
- Component: hotspot
- Sub-Component: jfr
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2019-01-14
- Updated: 2020-04-27
- Resolved: 2019-01-15
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.
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 13 | Other |
|---|---|
13 b04Fixed  |
openjdk8u262Fixed |
Related Reports
|
Relates :
|
Description
JfrRecorder::is_disabled is called early during bootstrap, and uses JVMFlag::find_flag directly to check whether the -XX:-FlightRecorder has been set on the command line. Using the FLAG_IS_CMDLINE macro from global_extensions has the same effect cleans it up and might avoid a linear scan. Also clean up enable() to use a macro to set the FlightRecorder value.
Comments
|