JDK-8253101 : Clean up CallStaticJavaNode EA flags
- Type: Enhancement
- Component: hotspot
- Sub-Component: compiler
- Affected Version: 16
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2020-09-14
- Updated: 2024-12-09
- Resolved: 2020-10-28
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
These two fields are reported as only written to, but not read from anywhere:
class CallStaticJavaNode : public CallJavaNode {
...
// Result of Escape Analysis
bool _is_scalar_replaceable;
bool _is_non_escaping;
}
There are accesses to AllocNode::{_is_scalar_replaceable,_is_non_escaping}, but not to CallStaticJavaNode.
This is either a bug, or more likely a leftover from EliminateAutoBox work, as these fields were introduced by JDK-6934604.
Comments
|