On Tue, 21 Apr 2026 16:45:55 GMT, Matias Saavedra Silva <[email protected]> wrote:
> Currently, scalarized calling conventions used by the compilers are > recalculated each runtime even though adapters can be stored in the AOT > cache. This change archives `_sig_cc` and `_sig_cc_ro` to avoid recomputing > them even when the adapter can be restored from the AOT archive. Verified > with tier 1-5 tests. > > --------- > - [x] I confirm that I make this contribution in accordance with the [OpenJDK > Interim AI Policy](https://openjdk.org/legal/ai). A couple of drive-by questions: * On top of `_sig_cc` and `_sig_cc_ro`, we also have `_sig`. Why don't we have to archive this? * At some point, I knew what "ro" stood for. I know we have 3 types of (compiled) entry points, and I took a look around the codebase a bit, but I genuinely couldn't find what it's an acronym form. Is there documentation anywhere, and if not, as a follow-up, could we write a couple of sentences (e.g., `CompiledEntrySignature`)? ------------- PR Comment: https://git.openjdk.org/valhalla/pull/2348#issuecomment-4295854182
