Some stubgen stubs rely on calls/branches into other stubgen stubs in order to handle special cases using internal entry points. which are currently not declared in the stub definitions file. Declarations should be provided to ensure that the call/branch target can be recognised during AOT stub save and relocated where needed during AOT stub restore. In order to ensure that the correct stubs are consumed when restoring AOT code two conventions should be followed. Code that produces an internal entry needs to save the entry address to the associated entry field. Code that consumes an internal entry should explicitly access the entry via the declared field.

Save and restore of entries is also simpler if all stubs have their first (and often only) entry at offset 0. On AArch64 some stubs generate data at the start of the code section and places the entry after the data. This should be corrected by following the convention of locating data embedded in the stub somewhere beyond offset 0 (e.g. at the end).