JDK-8232211 : Remove dead code from os.hpp|cpp
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 14
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2019-10-14
  • Updated: 2019-10-24
  • Resolved: 2019-10-16
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 14
14 b20Fixed
Related Reports
Relates :  
JDK-8160887 - os::elapsedVTime() is not consistent across platforms
Description
os.hpp has a number of dead and effectively unused methods that could be removed, including but not limited to:

 os::distribute_processes
 os::enable_vtime
 os::vtime_enabled
 os::default_file_open_flags
 os::do_you_want_to_debug (!?)
 os::is_debugger_attached
 SuspendResume::is_suspend_request

There's also os::bind_to_processor which is only implemented on Solaris and only used by CMS if enabling a diagnostic flag (BindCMSThreadToCPU) which defaults to false, which seems like a reasonable candidate for deprecation and removal.
Comments
URL: https://hg.openjdk.java.net/jdk/jdk/rev/562bf1878089 User: redestad Date: 2019-10-16 22:02:17 +0000
16-10-2019
Good pointer. Since JDK-8160350 then there is no platform where enable_vtime has any implementation. I think we can remove enable_vtime and vtime_enabled here and leave it up to JDK-8160887 to decide whether to move supports_vtime + elapsedVTime somewhere other than os
15-10-2019
For "vtime" also see JDK-8160887.
15-10-2019