RFR(S) 8139164: JVM should throw ClassFormatError for non-void methods named (original) (raw)
harold seigel harold.seigel at oracle.com
Mon Oct 26 12:31:31 UTC 2015
- Previous message: RFR(M): [ping!] 8139116: Fixes for warning "format not a string literal"
- Next message: RFR(S) 8139164: JVM should throw ClassFormatError for non-void methods named
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi,
Please review this small change to fix bug 8139164.
Recent proposed JVM-9 Spec changes (JDK-8130682 <https://bugs.openjdk.java.net/browse/JDK-8130682>) require throwing ClassFormatError exceptions for class file versions >= 51 for methods named that have one or more arguments or are not static. This fix implements that change.
Open webrev: http://cr.openjdk.java.net/~hseigel/bug_8139164/
JBS Bug: https://bugs.openjdk.java.net/browse/JDK-8139164
The fix was tested with JCK Lang, VM, and API java_lang tests, the UTE quick and split verifier tests, and the hotspot, JDK vm, java/io, java/lang, and java/util JTreg tests, and the tests included in this RFR.
Thanks, Harold
- Previous message: RFR(M): [ping!] 8139116: Fixes for warning "format not a string literal"
- Next message: RFR(S) 8139164: JVM should throw ClassFormatError for non-void methods named
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]