Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8135489 | emb-9 | Vladimir Ivanov | P3 | Resolved | Fixed | team |
JDK-8130139 | 8u66 | Vladimir Ivanov | P3 | Resolved | Fixed | b01 |
JDK-8130955 | 8u65 | Vladimir Ivanov | P3 | Resolved | Fixed | b05 |
JDK-8085964 | 8u60 | Vladimir Ivanov | P3 | Resolved | Fixed | b22 |
JDK-8137703 | emb-8u65 | Unassigned | P3 | Resolved | Fixed | b05 |
JDK-8130557 | emb-8u60 | Vladimir Ivanov | P3 | Resolved | Fixed | b22 |
It's caused by deopt count pollution. GWTs are heavily shared and deopt counts shouldn't be taken into account for GWT.
- backported by
-
JDK-8085964 GWT can be marked non-compilable due to deopt count pollution
-
- Resolved
-
-
JDK-8130139 GWT can be marked non-compilable due to deopt count pollution
-
- Resolved
-
-
JDK-8130557 GWT can be marked non-compilable due to deopt count pollution
-
- Resolved
-
-
JDK-8130955 GWT can be marked non-compilable due to deopt count pollution
-
- Resolved
-
-
JDK-8135489 GWT can be marked non-compilable due to deopt count pollution
-
- Resolved
-
-
JDK-8137703 GWT can be marked non-compilable due to deopt count pollution
-
- Resolved
-
- duplicates
-
JDK-8075273 MHs.GWT methods can be marked as non-compilable due to deopt count profile pollution
-
- Closed
-
- relates to
-
JDK-8063137 Never taken branches should be pruned when GWT LambdaForms are shared
-
- Closed
-