-
Bug
-
Resolution: Fixed
-
P3
-
7
-
b01
-
generic
-
generic
-
Verified
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2200230 | 7 | John Rose | P3 | Closed | Fixed | b112 |
| JDK-2205799 | 6u25 | John Rose | P3 | Resolved | Fixed | b01 |
In order to compile dynamically typed languages, the JVM needs to collect more dynamic typing profile information, and use the information it collects more completely.
Specifically:
- existing profiles on instanceof bytecodes need to be used (they are currently ignored)
- existing profiles on invocation receivers need to be used (they are currently used only in conjunction with inlining optimizations)
- certain type comparisons which appear monomorphic should be compiled to fail on uncommon traps, rather than normal slow path code
The following additional steps are requested by 6919064:
- profiles need to be collected on invokedynamic instructions
- profiles should also be collected on selected non-receiver arguments of method calls
Specifically:
- existing profiles on instanceof bytecodes need to be used (they are currently ignored)
- existing profiles on invocation receivers need to be used (they are currently used only in conjunction with inlining optimizations)
- certain type comparisons which appear monomorphic should be compiled to fail on uncommon traps, rather than normal slow path code
The following additional steps are requested by 6919064:
- profiles need to be collected on invokedynamic instructions
- profiles should also be collected on selected non-receiver arguments of method calls
- backported by
-
JDK-2205799 type profiles need to be exploited more for dynamic language support
-
- Resolved
-
-
-
- Closed
-
- relates to
-
JDK-6919069 client compiler needs to capture more profile information for tiered work
-
- Closed
-
-
-
- Open
-