JDK-8268720 : Unspecified checks on NameAndType constants should not be performed
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 18
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2021-06-14
  • Updated: 2024-06-18
  • Resolved: 2021-06-23
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 18
18 b04Fixed
Related Reports
Relates :  
JDK-8271536 - [lworld] VerifyError in hotspot/jtreg/runtime/classFileParserBug/NameAndTypeSig.java
Relates :  
JDK-8280480 - VM accepts an illegal method descriptor referred by CONSTANT_InvokeDynamic_info. name_and_type_index
Relates :  
JDK-8322655 - Allow NameAndType constants with special method names
Relates :  
JDK-8267650 - Better-defined JVM class file validation
Description
The JVM should not perform unspecified checks on NameAndType constants.  For example, the NameAndType constant <init>:()D is legal, per the specification, and should not cause a ClassFormatError unless and until it is referenced by a Methodref constant.
Comments
Changeset: f2e690e0 Author: Harold Seigel <hseigel@openjdk.org> Date: 2021-06-23 12:11:37 +0000 URL: https://git.openjdk.java.net/jdk/commit/f2e690e0ee503794cb50740170912697640d70ff
23-06-2021
ILW = MLM = P4
15-06-2021