United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
Bug ID: JDK-6693236 A class file whose version number is greater than 50.0 must be verified using the typechecker
JDK-6693236 : A class file whose version number is greater than 50.0 must be verified using the typechecker

Details
Type:
Bug
Submit Date:
2008-04-24
Status:
Closed
Updated Date:
2011-03-08
Project Name:
JDK
Resolved Date:
2011-03-08
Component:
hotspot
OS:
generic
Sub-Component:
runtime
CPU:
generic
Priority:
P3
Resolution:
Fixed
Affected Versions:
7
Fixed Versions:
hs19 (b03)

Related Reports
Backport:
Backport:
Backport:
Backport:

Sub Tasks

Description
According to 4.11.1 paragraph of JVMS3
"A class file whose version number is greater than to 50.0
must be verified using the typechecker rules"

Currently, if the typechecking fails, jdk 7 virtual machine
performs verification by type inference.

                                    

Comments
EVALUATION

evaluated
                                     
2010-05-18
EVALUATION

http://hg.openjdk.java.net/jdk7/hotspot-rt/hotspot/rev/e40a3601bc1f
                                     
2010-05-20
EVALUATION

http://hg.openjdk.java.net/jdk7/hotspot/hotspot/rev/e40a3601bc1f
                                     
2010-05-28
PUBLIC COMMENTS

The actual 4.11.1 paragraph of JVMS3 is

"A class file whose version number is greater than or equal to 50.0 must be verified using the typechecking rules given in this section. If, and only if, a class file???s version number equals 50.0, then if the typechecking fails, a virtual machine implementation may choose to attempt to perform verification by type inference.

The fix acts in the above fashion, i.e.,

If a v50 classfile has a stackmap, the stackmap is used for verification.
If no stackmap is present or verification using the stackmap fails, and the -XX
switch FailOverToOldVerifier is set, then the inference verifier is used. But if the classfile is v51 or higher no failover will occur if stackmap verification fails.
                                     
2010-08-19



Hardware and Software, Engineered to Work Together