Loading... (original) (raw)
- Type:
Bug
- Resolution: Fixed
- Priority:
P3
- Fix Version/s: 9
- Affects Version/s: 8u60, 9
If shared GWT causes too many recompilations, VM marks it as non-compilable.
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
(1 backported by, 1 duplicates, 1 relates to)