JDK-8203488 : Remove error generation from TransTypes
  • Type: Enhancement
  • Component: tools
  • Sub-Component: javac
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2018-05-21
  • Updated: 2019-01-18
  • Resolved: 2018-05-24
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 11
11 b16Fixed
Related Reports
Duplicate :  
JDK-8133247 - Use of HYPOTHETICAL flag in bridge generation logic leads to missing bridges in some cases
Relates :  
JDK-8013179 - assertion failure in javac when compiling with -source 1.6 -target 1.6
Relates :  
JDK-8216196 - No visibility bridges are created for generic methods
Relates :  
JDK-7007615 - java_util/generics/phase2/NameClashTest02 fails since jdk7/pit/b123.
Relates :  
JDK-8028739 - javac generates incorrect descriptor for MethodHandle::invoke
Description
TransTypes report user-facing errors in two conditions:

1) if there's a clash between bridge methods and user defined methods
2) if there's an actual/formal argument arity mismatch due to compiling sig poly methods with -target 6

Now, (1) is no longer an issue since we started carrying out override checks in Attr (see JDK-7007615); for (2) I believe a better fix for JDK-8013179 would be to eliminate much of the special casing associated to sig poly methods.