RFR(XS) 8076311: Java 9 process negative MaxTenuringThreshold in different way than Java 8 (original) (raw)
Dmitry Dmitriev dmitry.dmitriev at oracle.com
Fri Apr 3 09:49:48 UTC 2015
- Previous message: 8u60 backport RFR (M) 8067662: "java.lang.NullPointerException: Method name is null" from StackTraceElement.
- Next message: RFR(XS) 8076311: Java 9 process negative MaxTenuringThreshold in different way than Java 8
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hello,
Please review this small fix for JDK-8076311. Also, I need a sponsor for this fix, who can push it, because I'm not have a OpenJDK name.
Fix for JDK-6521376 add explicit processing of MaxTenuringThreshold XX option. When bad value for MaxTenuringThreshold is passed(e.g. negative value for unsigned option "-XX:MaxTenuringThreshold=-1"), then function print warning and continue execution with default value(0). This behavior differs from Java 8. Java 8 process this situation in common way for unsigned options, i.e. print waring and reports a error. So, I fix Java 9 MaxTenuringThreshold option processing.
Also, I add new test case to the test/gc/arguments/TestInitialTenuringThreshold.java to test this situation.
Open webrev: http://cr.openjdk.java.net/~ctornqvi/webrev/8076311/webrev.00/ <http://cr.openjdk.java.net/%7Ectornqvi/webrev/8076311/webrev.00/>
JBS bug: https://bugs.openjdk.java.net/browse/JDK-8076311
Tested: JPRT
Thank you, Dmitry
- Previous message: 8u60 backport RFR (M) 8067662: "java.lang.NullPointerException: Method name is null" from StackTraceElement.
- Next message: RFR(XS) 8076311: Java 9 process negative MaxTenuringThreshold in different way than Java 8
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]