RFR: 8349888: AOTMode=create crashes with EpsilonGC

[Aleksey Shipilev]

On Mon, 24 Feb 2025 04:26:09 GMT, Ioi Lam <iklam at openjdk.org> wrote:

> During AOT cache assembly, some classes may become excluded for various reasons. In the bug report, we have a class that was excluded because it wasn't loaded from a JAR file.
> 
> When AOT-resolving lambda call sites, we already exclude all sites that **refer** to excluded classes. However, we didn't exclude class sites that **live in** an excluded class. This PR fixes that.
> 
> This bug only affects EpsilonGC, which doesn't perform any collection. It doesn't affect other "real" collectors. Please see JBS issue for details.

Marked as reviewed by shade (Reviewer).

Marked as reviewed by shade (Reviewer).

test/hotspot/jtreg/runtime/cds/appcds/aotClassLinking/LambdaInExcludedClass.java line 67:

> 65:                 "-XX:+AOTClassLinking",
> 66:                 "-XX:+UnlockExperimentalVMOptions",
> 67:                 "-XX:+UseEpsilonGC",

I propose setting up some static heap size for this test to be extra-reliable. Since Epsilon does not collect, the amount of heap we get is the amount of allocations the application can possibly do. So if we ergonomically set too small heap, this test might fail accidentally.

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

PR Review: https://git.openjdk.org/jdk/pull/23741#pullrequestreview-2636387281
PR Review: https://git.openjdk.org/jdk/pull/23741#pullrequestreview-2636392386
PR Review Comment: https://git.openjdk.org/jdk/pull/23741#discussion_r1967258122