-
Type:
Bug
-
Resolution: Fixed
-
Priority:
P4
-
Affects Version/s: 8u40
-
Component/s: core-libs
-
b40
-
generic
-
generic
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8085537 | emb-9 | Attila Szegedi | P4 | Resolved | Fixed | team |
| JDK-8065530 | 8u45 | Attila Szegedi | P4 | Resolved | Fixed | b01 |
| JDK-8064717 | 8u40 | Attila Szegedi | P4 | Resolved | Fixed | b15 |
| JDK-8070519 | emb-8u47 | Attila Szegedi | P4 | Resolved | Fixed | team |
From Hannes.
Issue 1 just adds compile time. Issue 2 should be investigated.
1) I think the NodeVisitor in ApplySpecialization#hasApplies will enter into nested functions. Shouldn't it just look at the current function?
2) I wonder how hot the TransformFailedException constructor may get. Should we worry about string concatenation there?
Issue 1 just adds compile time. Issue 2 should be investigated.
1) I think the NodeVisitor in ApplySpecialization#hasApplies will enter into nested functions. Shouldn't it just look at the current function?
2) I wonder how hot the TransformFailedException constructor may get. Should we worry about string concatenation there?
- backported by
-
JDK-8064717 Trivial bugfixing and exception reuse in ApplySpecialization
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-