JDK-6491544 : Compiling try-finally within code size limit
  • Type: Enhancement
  • Component: tools
  • Sub-Component: javac
  • Affected Version: 6
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • OS: generic
  • CPU: generic
  • Submitted: 2006-11-09
  • Updated: 2024-04-12
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.
Other
tbdUnresolved
Related Reports
Relates :  
JDK-6464451 - javac in 5.0ux can not compile try-catch block which has a lot of "return"
Relates :  
JDK-4739388 - regression: javac generates too much bytecode for deply nested try-finally
Description
The amount of code per method is limited to 64K bytes by the sizes of the indices 
in the exception_table of the Code attribute, in the LineNumberTable attribute, 
in the LocalVariableTable attribute, and in the StackMapTable attribute (JVMS 2nd
edition 4.10).

After inlining subroutine code (4640034), some applications with extreme styles 
such as deeply nested finally blocks, or huge amount of exiting paths in try or
synchronized blocks, would fail to compile because code size exceeds limit. 
It was temporarily fixed in JDK 1.4.2 by introducing a command-line flag to 
control how much inlining happens for finally blocks (4739388). After jsr/ret
instructions are eliminated in JDK 6, the above workaround will no longer work.
Comments
EVALUATION We need a general solution to ensure backward compatibility. More specifically, a souce code compiled in older javac should still be able to compile in current javac.
09-11-2006