JDK-8253311 : Cleanup relocInfo constructors
- Type: Enhancement
- Component: hotspot
- Sub-Component: compiler
- Affected Version: 16
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2020-09-17
- Updated: 2024-11-22
- Resolved: 2020-09-21
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 b17Fixed  |
Related Reports
|
Relates :
|
|
|
Relates :
|
Description
The public relocInfo constructor uses assignment of (*this) from a new relocInfo created by one of the private constructors. This appears to be a clumsy mimicking of constructor delegation But with C++11 we now have real constructor delegation and can avoid contortions while not requiring code duplication or introducing a shared "initialization" function for the parts common among the various constructors.
Comments
|