How to deal with "target address out of range." in AOT

[AY268]

I am trying to use WAMR on Android and built a large AOT file.

However, I'm encountering a problem with the error message: "AOT module load failed: target address out of range."

This issue occurs in the do_text_relocation function within the aot_loader.c file, at the code block:

if (!apply_relocation(
    module, aot_text, aot_text_size, relocation->relocation_offset,
    relocation->relocation_addend, relocation->relocation_type,
    symbol_addr, symbol_index, error_buf, error_buf_size))

The values for these parameters are as follows:

I wonder how to deal with it.

[yamt]

what version of wamr are you using?
cf. #3743

[AY268]

what version of wamr are you using? cf. #3743

I run on the main branch up to commit b6dea22, but still have this problem.

[yamt]

the address of the native function seems too far from aot text for call26.
probably you can use large model (--size-level=0) to work it around.

[eloparco]

We're hitting the same condition

wasm-micro-runtime/core/iwasm/aot/arch/aot_reloc_arm.c

Line 362 in 510bb11

"target address out of range.");

on many Android devices in production.

Apart from changing the size level (that's not an option for us), are there other mitigations/workarounds? Ideally something on the wamrc side

[denizsokmen]

--enable-indirect-mode seems to be providing a path forward as I don't see JUMP24 relocations being emitted, however it still emits aeabi_ builtins despite disabling llvm intrinsics which may be a problem if PLT is not within the 32MB range. Is there a documentation around AOT format and relocations it uses? How does indirect mode eliminate the relocations? (just read the code, seems to hardcode an indirect call table at a certain offset from execenv)