RFR: 8362504: AArch64: Replace MOVZ+MOVK+MOVK with ADRP+ADD

[Fei Gao]

On Wed, 20 Aug 2025 08:44:30 GMT, Andrew Haley <aph at openjdk.org> wrote:

> > In short, in "production" run we need to know what code we are working on/patching: AOTed or normal JITed.
> 
> Or code should be the same.

Would it make sense to disable the reachability-based optimization when `AOTCodeCache::is_on()` returns true?
In this case, we would always emit `mov` triples for foreign calls if AoT is involved, whether dumping or using the AoT code cache.

For calls that must relocate into the code cache, we already always emit `adrp + add`, ensuring consistent behavior regardless of whether the code is AOT-compiled or JIT-compiled.

What do you think? Thanks!

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

PR Comment: https://git.openjdk.org/jdk/pull/26653#issuecomment-3206574431