-
Bug
-
Resolution: Fixed
-
P3
-
hs25
-
b61
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8029495 | 8 | Harold Seigel | P3 | Closed | Fixed | b119 |
Given an invokespecial of the form:
invokespecial I.m()V
Where I is an interface, it must be the case that the calling class/interface has I as a direct superinterface. See Lambda Spec, 0.6.3, Part J, 4.9.2.
I have been told that HotSpot currently allows a reference to an indirect superinterface. This should be prohibited, just like references to methods in classes unrelated to the calling class.
invokespecial I.m()V
Where I is an interface, it must be the case that the calling class/interface has I as a direct superinterface. See Lambda Spec, 0.6.3, Part J, 4.9.2.
I have been told that HotSpot currently allows a reference to an indirect superinterface. This should be prohibited, just like references to methods in classes unrelated to the calling class.
- backported by
-
JDK-8029495 InterfaceMethodref for invokespecial must name a direct superinterface
-
- Closed
-
- is blocked by
-
-
- Closed
-