-
Enhancement
-
Resolution: Fixed
-
P3
-
7
-
b38
-
generic
-
generic
-
Verified
It is likely that the Pack200 driver will crash on inputs which include new JDK 7 bytecode features, such as those introduced by JSR 292.
These features include:
- invokedynamic instructions
- CONSTANT_InvokeDynamic CP entries
- CONSTANT_MethodHandle CP entries
- CONSTANT_MethodType CP entries
The JSR 200 EG needs to issue a maintenance release that takes into account these new formats, especially the new CP entry types.
Perhaps the new Pack200 format should "future proof" the CP by allowing layout declarations for unknown CP types. On the other hand, JDK 8 is likely to include unforeseeable class file changes, so a a maintenance release for JDK 8 is desirable also.
These features include:
- invokedynamic instructions
- CONSTANT_InvokeDynamic CP entries
- CONSTANT_MethodHandle CP entries
- CONSTANT_MethodType CP entries
The JSR 200 EG needs to issue a maintenance release that takes into account these new formats, especially the new CP entry types.
Perhaps the new Pack200 format should "future proof" the CP by allowing layout declarations for unknown CP types. On the other hand, JDK 8 is likely to include unforeseeable class file changes, so a a maintenance release for JDK 8 is desirable also.
- relates to
-
JDK-6982312 (pack200) pack200 fails with the jdk7 class files
-
- Closed
-
-
JDK-6982999 tools must support -target 7 bytecodes
-
- Closed
-
-
JDK-7050936 (pack200) Support version 52.0 class files
-
- Closed
-
-
JDK-8062335 Pack200 Java implementation differs from C version, outputs unused UTF8 for BootstrapMethods
-
- Closed
-