RFR: 8295724: VirtualMachineError: Out of space in CodeCache for method handle intrinsic
Dean Long
dlong at openjdk.org
Thu Nov 3 01:26:11 UTC 2022
On Wed, 2 Nov 2022 22:18:25 GMT, Richard Reingruber <rrich at openjdk.org> wrote:
> I think the continuation intrinsics (see `Method::is_continuation_native_intrinsic()`) are problematic too. There are no interpreted versions of them. It will be difficult to implement interpreted versions.
Good point. It's not really interpreted vs compiled that is important, it's eager-allocated vs lazy-allocated, and if we need a different one for every polymorphic signature. Somewhere in between lazy and eager is "delayed". We could chose a low-water mark, where the code cache has free space less than "LazyIntrinsicsSize" available, where we force these intrinsics to get generated if they weren't already generated lazily. The problem is the missing signature-independent interpreted _linkToNative and the fact that the compiled version depends on the polymorphic signature, forcing them to be generated lazily to handle all possible signatures.
-------------
PR: https://git.openjdk.org/jdk/pull/10933
More information about the hotspot-compiler-dev
mailing list