Allow enums to have more constants

[guw]

Please implement the enhancement done to javac which allows to compile enums with more constants.
https://bugs.openjdk.org/browse/JDK-8241798

A little test shows, that javac compiles ok but ecj fails with:

----------
1. ERROR in ...bazel-jdt-java-toolchain/ecj-test/src/BigEnum.java (at line 30)
	public enum BigEnum {
	            ^^^^^^^
The code for the static initializer is exceeding the 65535 bytes limit
----------
1 problem (1 error)

[szarnekow]

Quoting the ticket:

This is similar to what ecj is already doing

What do you expect from this ticket, @guw ?

[guw]

I have updated the description. Sample class for testing is available:
https://hg.openjdk.org/jdk/jdk/rev/97d5d0cd1085
https://github.com/openjdk/jdk/blob/master/test/langtools/tools/javac/enum/BigEnum.java

[stephan-herrmann]

If I read the JDK bug correctly, for some time ecj supported more enum constants than javac. Now that javac has improved, the situation may have reversed. It is unclear, however, how javac could become "better" than ecj simply by doing things "similar" to ecj.

What is the number of enum constants supported by ecj, by javac?

If javac can support more enum constants than ecj, by what strategy has this been achieved?

[guw]

Maybe the statement isn't fully correct, though?

For clarity, here is the full text:

This is similar to what ecj is already doing: instead of saving the values array to a static field that's initialized in the <clinit>, it just re-creates the array for every call to values(). That may be worth considering, although it may also have performance implications vs. initializing the values array upfront and using clone().