JDK-8255617 : Zero: purge the remaining bytecode interpreter profiling support
- Type: Enhancement
- Component: hotspot
- Sub-Component: runtime
- Affected Version: 8,11,15,16
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2020-10-29
- Updated: 2024-12-09
- Resolved: 2020-11-04
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 16 |
|---|
16 b23Fixed  |
Related Reports
|
Relates :
|
Description
All the stubs in interpreter/zero/bytecodeInterpreterProfiling.hpp are empty. History shows the whole thing gradually moved to template interpreter. We can probably simplify Zero code by dropping these empty stubs altogether. Arguably, this makes porting to new architectures a bit harder, but it seems that the proper stepping stone after Zero is implementing template interpreter anyway. On my TR 3970X, this improves: - Linux x86_64 Zero "make images" times from ~18 minutes to ~17.5 minutes
Comments
|