JDK-8266573 : Make sure blackholes are tagged for all JVMCI paths
- Type: Enhancement
- Component: hotspot
- Sub-Component: compiler
- Affected Version: 17
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2021-05-05
- Updated: 2021-05-13
- Resolved: 2021-05-06
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 17 |
|---|
17 b22Fixed  |
Related Reports
|
Relates :
|
Description
In post-integration comment to JDK-8259316, Tom says: "In this code, 6018336#diff-fa2433a762244542fec57f9d58dd3092bae74f354acf0ef33603a5f8306fd7daR995, the call to CompilerOracle::tag_blackhole_if_possible should be outside of the if. As written, methods won't be properly tagged for libgraal, only when used with the pure Java graal." See: https://github.com/openjdk/jdk/pull/2024#issuecomment-832834830
Comments
|