-
Bug
-
Resolution: Unresolved
-
P4
-
24
Inlining fails earlier for MemorySegment::reinterpret compared to other variants.
@ 5 java.lang.Class::getModule (5 bytes) accessor
@ 33 java.lang.System$2::ensureNativeAccess (11 bytes) inline (hot)
@ 7 java.lang.Module::ensureNativeAccess (299 bytes) inline (hot)
@ 1 java.lang.Module::moduleForNativeAccess (15 bytes) inline (hot)
FAILURE HERE -> @ 1 java.lang.Module::isNamed (13 bytes) failed to inline: inlining too deep
Details here https://gist.github.com/Spasi/513d57fc608d9b91bcd73751e71491d1
We should try adding @ForceInline annotations to some internal methods.
@ 5 java.lang.Class::getModule (5 bytes) accessor
@ 33 java.lang.System$2::ensureNativeAccess (11 bytes) inline (hot)
@ 7 java.lang.Module::ensureNativeAccess (299 bytes) inline (hot)
@ 1 java.lang.Module::moduleForNativeAccess (15 bytes) inline (hot)
FAILURE HERE -> @ 1 java.lang.Module::isNamed (13 bytes) failed to inline: inlining too deep
Details here https://gist.github.com/Spasi/513d57fc608d9b91bcd73751e71491d1
We should try adding @ForceInline annotations to some internal methods.
- links to
-
Review(master) openjdk/jdk/23460