8209385: CDS runtime classpath checking is too strict when only classes from the system modules are archived

Skip checking the path entries which are not being referenced during CDS dump time

Reviewed-by: jiangli, iklam
This commit is contained in:
Calvin Cheung 2018-08-17 14:50:59 -07:00
parent 15cef25bb0
commit 660c7e50f7
8 changed files with 122 additions and 20 deletions

View file

@ -49,6 +49,8 @@ private:
static jshort _app_class_paths_start_index;
// index of first modular JAR in shared modulepath entry table
static jshort _app_module_paths_start_index;
// the largest path index being used during CDS dump time
static jshort _max_used_path_index;
static bool _has_app_classes;
static bool _has_platform_classes;
@ -91,6 +93,12 @@ public:
static jshort app_module_paths_start_index() { return _app_module_paths_start_index; }
static jshort max_used_path_index() { return _max_used_path_index; }
static void set_max_used_path_index(jshort used_index) {
_max_used_path_index = used_index;
}
static void init_paths_start_index(jshort app_start) {
_app_class_paths_start_index = app_start;
}