comparison hotspot/src/share/vm/classfile/modules.cpp @ 46463:4bd2ca84df7a

8178604: JVM does not allow defining boot loader modules in exploded build after module system initialization Summary: Allow defining of boot loader modules after initialization but add locks to synchronize access to exploded build list Reviewed-by: dholmes, lfoltan
author hseigel
date Tue, 16 May 2017 09:33:49 -0400
parents 3c12af929e7d
children 388aa8d67c80
comparison
equal deleted inserted replaced
36:90c9501cf9ff 37:7c65fde833d8
447 (pkg_list->at(y))->as_C_string(), module_name); 447 (pkg_list->at(y))->as_C_string(), module_name);
448 } 448 }
449 } 449 }
450 450
451 // If the module is defined to the boot loader and an exploded build is being 451 // If the module is defined to the boot loader and an exploded build is being
452 // used, prepend <java.home>/modules/modules_name, if it exists, to the system boot class path. 452 // used, prepend <java.home>/modules/modules_name to the system boot class path.
453 if (loader == NULL && 453 if (loader == NULL && !ClassLoader::has_jrt_entry()) {
454 !ClassLoader::has_jrt_entry()) {
455 ClassLoader::add_to_exploded_build_list(module_symbol, CHECK); 454 ClassLoader::add_to_exploded_build_list(module_symbol, CHECK);
456 } 455 }
457 } 456 }
458 457
459 void Modules::set_bootloader_unnamed_module(jobject module, TRAPS) { 458 void Modules::set_bootloader_unnamed_module(jobject module, TRAPS) {