RFR: 8311071: Avoid SoftReferences in LambdaFormEditor and MethodTypeForm when storing heap objects into AOT cache [v3]

[Ioi Lam]

On Wed, 18 Sep 2024 12:15:08 GMT, Claes Redestad <redestad at openjdk.org> wrote:

> How does archiving and resolution of the linked `MethodType` instances work? In particular how does archiving fill up the `MethodType::internTable` to ensure `MethodType` uniqueness?

The details are in the next PR (https://github.com/openjdk/jdk/pull/21143) which is still in draft state. 

At the end of AOT cache assembly phase, the JVM (in `MetaspaceShared::preload_and_dump_impl(()`) upcalls `MethodType::createArchivedObjects()` to copy all MethodTypes into a side table (`MethodType::AOTHolder::archivedMethodTypes`).

During the production run, we first look up from the side table, before checking/interning in the main table.

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

PR Comment: https://git.openjdk.org/jdk/pull/21049#issuecomment-2369125142