-
Bug
-
Resolution: Duplicate
-
P4
-
None
-
8
-
None
- Checks relating to `final` classes and methods, and an absent superclass, occur in practice at class loading time, not verification time. They should appear in 5.3.5, not 4.10. (There's actually quite a lot of overhead in 4.10 to support these checks. With the change, verification is only concerned with methods with code.)
- The rules preventing circularity in superclasses/superinterfaces are imprecise.
- Class loading behavior when there are multiple threads attempting to load a class is unspecified.
- The behavior when a `loadClass` method does not behave as expected or throws an exception is not fully specified.
- The notion of creating an "array class" does not belong in a discussion about class loading. (The section is about processing `class` files, not accounting for every java.lang.Class instance.)
- duplicates
-
JDK-8260516 JVMS changes for Sealed Classes
-
- Resolved
-
- relates to
-
JDK-8233863 4.7: Simplify and clarify the rules for optional attribute validation
-
- Open
-
-
JDK-8322507 5.3, 5.4: Better specify the treatment of array types
-
- Open
-
-
JDK-8258138 4.10: Eliminate redundant 'final' checks in verification
-
- In Progress
-
-
JDK-8243582 5.3.5: Perform 'final' error checks during class loading, not verification
-
- Resolved
-
-
JDK-8202620 5.3: Clarify handling of exceptions thrown by ClassLoaders
-
- Resolved
-
-
JDK-8268628 5.3.5: Properly specify how circularity checking & multi-threading work
-
- Resolved
-
-
JDK-8233854 4.8: Clarify which checks occur during format checking
-
- In Progress
-