Bug 3177 - 64kb method should be a configurable problem (1FJHGVF)
Summary: 64kb method should be a configurable problem (1FJHGVF)
Status: RESOLVED WONTFIX
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.0   Edit
Hardware: All Windows 98
: P3 normal (vote)
Target Milestone: 2.0 M1   Edit
Assignee: Philipe Mulet CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-10-10 22:50 EDT by Philipe Mulet CLA
Modified: 2002-01-11 09:04 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Philipe Mulet CLA 2001-10-10 22:50:47 EDT
Sun javac 1.2.2 will only issue a warning by default:

A.java:3: This code requires generating a method with more than 64K bytes.  Virtual machines may refuse the resulting class file.
        int[] intarray = {
                         ^
1 warning

NOTES:

Philippe (10/4/99 3:16:38 PM)
	In presence of wide branches in such code, javac is not using gotow bytecodes (like us), thus leading to 
	illegal code generation. Need to see any use for only making it a warning in order to comply with Sun's behavior.

Philippe (10/4/99 4:07:19 PM)
	New javac 1.3 will properly generate a goto_w bytecodes, and not even complain for a warning.
	Then we should also fix the bytecode and issue a warning.

PM (7/25/2001 1:59:55 PM)
	We should only fix the bytecode, and make a potential warning (in case embedded customer are using it).
Comment 1 Philipe Mulet CLA 2001-10-11 12:06:18 EDT
Bytecode generation got fixed. Nobody mentionned needing a warning for it.
Closing
Comment 2 DJ Houghton CLA 2001-10-23 23:50:42 EDT
PRODUCT VERSION:
lf315