AArch64: Use lastITable cache for interface call dispatching

[Akira1Saitoh]

This commit extends the existing interface call dispatching code of AArch64 codegen to exploit cached lastITable field in J9Class. buildInterfaceCall function is updated to generate The code for lastITable cache lookup after the code for checking the second PIC slot. Until the second slot is populated, lastITable cache lookup always fails to avoid filling PIC slots with infrequent call targets. See OpenJ9 #8390 for more details.
After the second slot is filled, the lastITable cache lookup is enabled by patching the b.al (branch always) instruction in the lookup code to b.ne (branch if not equal).
Recompilation code is also updated to properly handle the new instruction sequence generated by updated buildInterfaceCall function.

Resolves #8400
Signed-off-by: Akira Saitoh [email protected]

[knn-k]

Jenkins test sanity alinux64,amac jdk17

[knn-k]

Jenkins test sanity amac jdk17

[knn-k]

I launched amac build again because the previous one failed with the following error:

https://openj9-jenkins.osuosl.org/job/Build_JDK17_aarch64_mac_Personal/488/

[2023-09-21T07:27:10.564Z] Waiting for next available executor on ‘ci.role.build&&hw.arch.aarch64&&sw.os.mac’
ERROR: Cannot resume build because FlowNode 52 for FlowHead 1 could not be loaded. This is expected to happen when using the PERFORMANCE_OPTIMIZED durability setting and Jenkins is not shut down cleanly. Consider investigating to understand if Jenkins was not shut down cleanly or switching to the MAX_SURVIVABILITY durability setting which should prevent this issue in most cases.
Finished: FAILURE

[knn-k]

The AArch64 Linux job failed in the same way as the macOS job above. It looks likes an infrastructural problem.

[2023-09-21T08:09:53.085Z] Starting building: Test_openjdk17_j9_sanity.functional_aarch64_linux_Personal #340
Creating placeholder flownodes because failed loading originals.
ERROR: Cannot resume build because FlowNode 110 for FlowHead 1 could not be loaded. This is expected to happen when using the PERFORMANCE_OPTIMIZED durability setting and Jenkins is not shut down cleanly. Consider investigating to understand if Jenkins was not shut down cleanly or switching to the MAX_SURVIVABILITY durability setting which should prevent this issue in most cases.
Finished: FAILURE

[knn-k]

Jenkins test sanity alinux64 jdk17