JDK-6420151 : need to improve byfile compile policy to eliminate footprint issues
  • Type: Bug
  • Component: tools
  • Sub-Component: javac
  • Affected Version: 6
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2006-05-01
  • Updated: 2011-05-18
  • Resolved: 2011-05-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 7 Other
7 b38Fixed OpenJDK6Fixed
Related Reports
Relates :  
JDK-4834690 - javac generates fewer class files than it could on errors
Relates :  
JDK-6382700 - Default compile policy in javac causes footprint issues
Description
The byfile compile policy currently causes attribution of all files before any code is generated. This defeats other optimizations during code generation, such as discarding method bodies once they have been generated. As a result, the compiler cannot compile as many files as before, with the byfile policy.
Comments
EVALUATION Two changes are required -- the various "phase" methods on JavaCompiler should be changed to use lazy iterators instead of Lists -- the todo list should be more byfile-friendly, so that it is possible to iterate all the todo elements for a file together. This could be done by replacing the current ListBuffer<Env<AttrContext>> with a Map<JavaFileObject,ListBuffer<Env<AttrContext>>>
01-05-2006