-
Bug
-
Resolution: Fixed
-
P4
-
hs22, 7
-
b52
-
generic
-
generic
-
Not verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8017940 | 7u45 | Christian Thalinger | P4 | Closed | Fixed | b01 |
JDK-8002744 | 7u40 | Christian Thalinger | P4 | Closed | Fixed | b01 |
The Hotspot reference implementation for JSR 292 uses a conservative technique for constructing method handle nodes: It defers the low-level data structure initialization to native C++ code accessed via JNI.
Now that the internal implementation schema for method handle nodes is better understood, we should move the data structure initialization code into trusted Java code.
This will enable the dynamic compiler to make appropriate optimizations at points where method handles are created. This is important, for example, for the bindTo and asInstance operations, which closures are likely to use, and which need to be aggressively optimized.
Now that the internal implementation schema for method handle nodes is better understood, we should move the data structure initialization code into trusted Java code.
This will enable the dynamic compiler to make appropriate optimizations at points where method handles are created. This is important, for example, for the bindTo and asInstance operations, which closures are likely to use, and which need to be aggressively optimized.
- backported by
-
JDK-8002744 JSR 292 method handle creation should not go through JNI
-
- Closed
-
-
JDK-8002745 JSR 292 method handle creation should not go through JNI
-
- Closed
-
-
JDK-8002746 JSR 292 method handle creation should not go through JNI
-
- Closed
-
-
JDK-8017940 JSR 292 method handle creation should not go through JNI
-
- Closed
-
- duplicates
-
JDK-7071693 JSR 292: native method calls slow down method handle constructor execution
-
- Closed
-