JDK-8230762 : Change MacroAssembler::debug32/64 to use fatal instead of assert
- Type: Enhancement
- Component: hotspot
- Sub-Component: compiler
- Affected Version: 14
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2019-09-09
- Updated: 2019-09-26
- Resolved: 2019-09-12
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 14 |
|---|
14 b15Fixed  |
Related Reports
|
Relates :
|
Description
As a follow-up to JDK-8225653, MacroAssembler::debug32/64 should use fatal() instead of assert() to also crash in a product build. Any usages of debug32/64 should be cleaned up in case they are expected to return. See also: https://mail.openjdk.java.net/pipermail/hotspot-compiler-dev/2019-September/034987.html
Comments
|