| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2212423 | 8 | Tom Rodriguez | P2 | Closed | Fixed | b01 |
| JDK-2210179 | 7 | Tom Rodriguez | P2 | Closed | Fixed | b144 |
| JDK-2212421 | hs22 | Tom Rodriguez | P2 | Resolved | Fixed | b01 |
This is a follow-up to 6998541.
Customers have observed that inlining some kinds of method handles tickles unexpected paths in methodHandleWalk.cpp.
Known cases:
- http://mail.openjdk.java.net/pipermail/mlvm-dev/2011-May/003060.html
- http://mail.openjdk.java.net/pipermail/mlvm-dev/2011-May/003055.html
- asSpreader adapters
There should be "lose" calls on paths we don't expect, so the method handle walker can back out cleanly and fail the inlining.
Customers have observed that inlining some kinds of method handles tickles unexpected paths in methodHandleWalk.cpp.
Known cases:
- http://mail.openjdk.java.net/pipermail/mlvm-dev/2011-May/003060.html
- http://mail.openjdk.java.net/pipermail/mlvm-dev/2011-May/003055.html
- asSpreader adapters
There should be "lose" calls on paths we don't expect, so the method handle walker can back out cleanly and fail the inlining.
- backported by
-
JDK-2212421 JSR 292 inlining causes crashes in methodHandleWalk.cpp
-
- Resolved
-
-
-
- Closed
-
-
-
- Closed
-
- relates to
-
JDK-7047697 MethodHandle.invokeExact call for wrong method causes VM failure if run with -Xcomp
-
- Closed
-
-
JDK-6998541 JSR 292 implement missing return-type conversion for OP_RETYPE_RAW
-
- Closed
-