Way to guarantee generated indirect call is via memory?

I’d like to generate an indirect call instruction that will end up as a call via memory and not register.

The address of the target is a constant.

For example, something like

%25 = load i64, i64* @get_Now

%26 = inttoptr i64 %25 to i64 ()*

%27 = call i64 %26()

may end up as

mov rsi,qword ptr [00007FF658381070]

call rsi

or as

call qword ptr [00007FF658381070]

If I want to guarantee that the second form is always used, how would I go about that?

One possibility is to use patchpoints (http://llvm.org/docs/StackMaps.html#id9). Are there any other alternatives?

Eugene

One possibility is to use patchpoints
(http://llvm.org/docs/StackMaps.html#id9). Are there any other alternatives?

Have you tried using a small code model?

-- Sanjoy

Yes, I tried small code model. It does help some but still doesn't guarantee that optimizations won't decide to hoist the address into a register.

Eugene

Dear Eugene,

I think the best way to do this is to generate inline assembly code at the LLVM IR level that uses the memory-based addressing mode that you want. Any other approach could break with changes/enhancements to the LLVM code generator.

The only other way to do this is to write an LLVM MachineFunctionPass, but that is probably overkill for what you're trying to do.

Regards,

John Criswell

The two options listed so far (inline asm and patchable code via patchpoints/statepoints) are definitely your best options if the call via memory is a functional requirement.

If you’re willing to live with some chance LLVM emits different code, you could try representing the function pointer as an external global variable in the Module with the call and then linking it with a Module which contains the constant value of the global. My guess - haven’t checked - is that this would generally result in the code generation you want. This would mostly be useful for an experiment or an optimization, not for fulfilling a functional or ABI requirement.

Philip