RFR: 8364929: Assign unique id to each AdapterBlob stored in AOTCodeCache

Vladimir Kozlov kvn at openjdk.org
Tue Sep 30 16:06:00 UTC 2025


On Mon, 29 Sep 2025 16:22:45 GMT, Ashutosh Mehra <asmehra at openjdk.org> wrote:

> This patch assigns unique id to each AdapterHandlerEntry so as to avoid using hash computed from AdapterFingerPrint which may not be unique. Unique id allows AOTCodeCache to locate the AdapterBlob being requested to be loaded.
> 
> Testing:
> Before this patch `runtime/cds/appcds/aotClassLinking/StringConcatStress.java` emits warning messages in the production run:
> 
> [0.009s][warning][aot,codecache,stubs] Saved blob's name 'LIIDIIIDL' is different from the expected name 'LIIDIIDL'
> [0.009s][warning][aot                ] Failed to link AdapterHandlerEntry (fp=LIIDIIDL) to its code in the AOT code cache
> [0.009s][warning][aot,codecache,stubs] Saved blob's name 'IILLLLIIIIII' is different from the expected name 'IILLLLLILIII'
> [0.009s][warning][aot                ] Failed to link AdapterHandlerEntry (fp=IILLLLLILIII) to its code in the AOT code cache
> 
> With this patch, such warnings are not seen at all

How you insure that the order of adapters generation is the same in assembly and production runs?

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

PR Review: https://git.openjdk.org/jdk/pull/27553#pullrequestreview-3285741851


More information about the hotspot-dev mailing list