JDK-8015402 : Lambda metafactory should not attempt to generate bridge methods
  • Type: Sub-task
  • Component: core-libs
  • Sub-Component: java.lang.invoke
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • CPU: unknown
  • Submitted: 2013-05-24
  • Updated: 2017-05-17
  • Resolved: 2013-06-18
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.
JDK 8
8 b96Fixed
Related Reports
Blocks :  
JDK-8016281 - The SAM method should be passed to the metafactory as a MethodType not a MethodHandle
Relates :  
JDK-8013789 - Compiler should emit bridges in interfaces
Relates :  
JDK-8017044 - anti-delta fix for 8015402
Description
As part of JDK-8013789, responsibility for bridge methods moves to the static compiler.  The metafactory should stop trying to guess which bridge methods to wire, and only wire the methods that have been requested by the compiler.  

In turn, this requires a slight modification ot the API of the alternate metafacory, where the compiler can provide an optional list of method signatures to bridge.
Comments
SQE has looked at the fix and decided no additional tests are needed.
11-09-2013
Fix under review
30-05-2013