8076311: Java 9 process negative MaxTenuringThreshold in different way than Java 8
Corrected processing of invalid MaXTenuringThreshold Reviewed-by: jmasa, dholmes, kbarrett
This commit is contained in:
parent
2a4fe40ee2
commit
5f589f20aa
@ -3150,7 +3150,8 @@ jint Arguments::parse_each_vm_init_arg(const JavaVMInitArgs* args,
|
||||
uintx max_tenuring_thresh = 0;
|
||||
if(!parse_uintx(tail, &max_tenuring_thresh, 0)) {
|
||||
jio_fprintf(defaultStream::error_stream(),
|
||||
"Invalid MaxTenuringThreshold: %s\n", option->optionString);
|
||||
"Improperly specified VM option 'MaxTenuringThreshold=%s'\n", tail);
|
||||
return JNI_EINVAL;
|
||||
}
|
||||
FLAG_SET_CMDLINE(uintx, MaxTenuringThreshold, max_tenuring_thresh);
|
||||
|
||||
|
@ -70,6 +70,7 @@ public class TestInitialTenuringThreshold {
|
||||
runWithThresholds(10, 0, true);
|
||||
runWithThresholds(9, 8, true);
|
||||
runWithThresholds(-1, 8, true);
|
||||
runWithThresholds(0, -1, true);
|
||||
runWithThresholds(8, -1, true);
|
||||
runWithThresholds(16, 8, true);
|
||||
runWithThresholds(8, 17, true);
|
||||
|
Loading…
Reference in New Issue
Block a user