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

[Vladimir Kozlov]

On Tue, 30 Sep 2025 16:35:01 GMT, Ashutosh Mehra <asmehra at openjdk.org> wrote:

> Adapters are not generated again in the production run. The adapter id is part of the AdapterHandlerEntry and they are stored in the AOTCache in the assembly run. In the production run when they are loaded back, we get the max id and use it populate the running id counter. Any new adapter generated in the production run gets the next id. Does that help?

Do we have guarantee that we load AOT adapters before any new adapter is generated?

Also if hash is not used we don't need related methods. Right?

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

PR Comment: https://git.openjdk.org/jdk/pull/27553#issuecomment-3353002107