JDK-8238765 : PhaseCFG::schedule_pinned_nodes cannot handle precedence edges from unmatched CFG nodes correctly
- Type: Bug
- Component: hotspot
- Sub-Component: compiler
- Affected Version: 11,12,13,14,15
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- Submitted: 2020-02-10
- Updated: 2022-06-27
- Resolved: 2020-02-17
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 11 | JDK 13 | JDK 15 |
|---|---|---|
| 11.0.8-oracleFixed | 13.0.4Fixed | 15 b11Fixed  |
Related Reports
|
Relates :
|
Description
The internal testing for JDK 14 revealed a case where a precedence edge from a not yet matched CFG node (i.e. a node in the middle of a block) was processed by PhaseCFG::schedule_pinned_nodes. As a result, the is_dominator() check returned a wrong answer which later resulted in a segfault due to a wrong block ordering produced by GCM together with StressGCM. In this case, a load was moved before the associated NULL check. This, however, was only observed by using ZGC but it appears to be unrelated to ZGC itself. With ZGC, an ArrayAllocation expands before a LoadP which is used for a LoadRange node later in such a way that PhaseCFG::schedule_pinned_nodes faces a precedence edge for that LoadRange node from a CFG node that is not yet machted (i.e. in the middle of a block). The internal test used -XX:+UseZGC and -XX:+StressGCM.
Comments
|