On Thu, 16 Apr 2026 14:51:27 GMT, Matthias Baesken <[email protected]> wrote:

> When building hotspot on linuxx86_64/gcc with LTO enabled 
> (--enable-jvm-feature-link-time-opt), we get various test errors in the 
> serviceability/sa area.
> Example serviceability/sa/CDSJMapClstats.java
> 
> 
> finding class loader instances ..java.lang.InternalError: Metadata does not 
> appear to be polymorphic
> at 
> jdk.hotspot.agent/sun.jvm.hotspot.types.basic.BasicTypeDataBase.findDynamicTypeForAddress(BasicTypeDataBase.java:223)
> at 
> jdk.hotspot.agent/sun.jvm.hotspot.runtime.VirtualBaseConstructor.instantiateWrapperFor(VirtualBaseConstructor.java:104)
> at 
> jdk.hotspot.agent/sun.jvm.hotspot.oops.Metadata.instantiateWrapperFor(Metadata.java:77)
> at 
> jdk.hotspot.agent/sun.jvm.hotspot.memory.SystemDictionary.getClassLoaderKlass(SystemDictionary.java:102)
> at 
> jdk.hotspot.agent/sun.jvm.hotspot.tools.ClassLoaderStats.printClassLoaderStatistics(ClassLoaderStats.java:93)
> at 
> jdk.hotspot.agent/sun.jvm.hotspot.tools.ClassLoaderStats.run(ClassLoaderStats.java:78)
> at jdk.hotspot.agent/sun.jvm.hotspot.tools.JMap.run(JMap.java:121)
> at jdk.hotspot.agent/sun.jvm.hotspot.tools.Tool.startInternal(Tool.java:278)
> at jdk.hotspot.agent/sun.jvm.hotspot.tools.Tool.start(Tool.java:241)
> at jdk.hotspot.agent/sun.jvm.hotspot.tools.Tool.execute(Tool.java:134)
> at jdk.hotspot.agent/sun.jvm.hotspot.tools.JMap.main(JMap.java:202)
> at jdk.hotspot.agent/sun.jvm.hotspot.SALauncher.runJMAP(SALauncher.java:344)
> at jdk.hotspot.agent/sun.jvm.hotspot.SALauncher.main(SALauncher.java:507)
> 
> 
> Seems we have to avoid elimination of the Metadata vtable ; this can be 
> achieved by linker flags or by modifying class Metadata.
> 
> ---------
> - [x] I confirm that I make this contribution in accordance with the [OpenJDK 
> Interim AI Policy](https://openjdk.org/legal/ai).

https://github.com/openjdk/jdk/pull/12743/changes Seems like that one went with 
introducing a new virtual method and overriding it in the subclass. Also not 
great, but it's a starting point to see what is needed to stop the vtable from 
being removed.

-------------

PR Comment: https://git.openjdk.org/jdk/pull/30771#issuecomment-4279256080

Reply via email to