| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8248100 | 16 | Yumin Qi | P4 | Resolved | Fixed | team |
http://hg.openjdk.java.net/jdk/jdk/file/7ef41e83066b/src/hotspot/share/classfile/systemDictionary.cpp#l1268
is_shared_class_visible() might be time consuming because it needs to look up PackageEntry and ModuleEntry. However, if we are running the JVM without any of the following:
bootclasspath append
--limit-modules
--upgrade-module-path
is_shared_class_visible() will always return true, so we can skip the call to improve start-up time.
is_shared_class_visible() might be time consuming because it needs to look up PackageEntry and ModuleEntry. However, if we are running the JVM without any of the following:
bootclasspath append
--limit-modules
--upgrade-module-path
is_shared_class_visible() will always return true, so we can skip the call to improve start-up time.
- backported by
-
JDK-8248100 Avoid calling is_shared_class_visible() in SystemDictionary::load_shared_class()
-
- Resolved
-
- relates to
-
JDK-8247449 Revisit the argument processing logic for MetaspaceShared::disable_optimized_module_handling()
-
- Resolved
-
-
JDK-8247388 Minimal build broken after JDK-8240245 (undefined reference to `MetaspaceShared::_use_optimized_module_handling')
-
- Closed
-