JDK-8058318 : compiler changes for eager interface initialization
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 8u40,9
  • Priority: P2
  • Status: Closed
  • Resolution: Other
  • OS: generic
  • CPU: generic
  • Submitted: 2014-09-12
  • Updated: 2014-10-10
  • Resolved: 2014-10-10
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
8u40Resolved 9Resolved
Related Reports
Relates :  
Relates :  
JDK-8043190 is proposing specification enhancements for JSR-337 as part of a Maintenance Review. JDK-8043275 was the initial implementation bug filed to support lazy interface initialization and owned by runtime. I have done the changes to the linkResolver and cpCache so that so far testing -Xint works. I have also done initial changes for MethodHandles, although I do not know the best way to test them.

The streams combo tests do not pass with the compiler enabled and this work requires compiler expertise. We need to jointly submit changes so the entire system works.

This is requested for 8u40.
I think it would be really awesome if this bug included a link to exactly the changes in behavior that are expected. Not a link to a discussion of the pros and cons of the alternative behaviors, or discussions of diffs that might be applied, but a link to the actual resolution of the issue. Because otherwise, I get to spend time trying to figure out what is intended. Good thing there's no urgent need for this.

As this needs to go into 8u40 this has top priority and needs to be worked on immediately.

ILW=mismatch updated jvms;iface init on default method invocation;none=HM/LH=>P2