search for: r_xxx_movi

...> When I look at the text section (llvm-objdump -s output), I see this > > 0000 00c2 > > This is the correct MOVI opcode but the instead of the 0s, I should see the address of 'date' I don't think you should see "date" there yet. That's the whole reason for R_XXX_MOVI to exist: it tells the linker to insert the address of date when converting this .o file into a final executable. The only time you might see something in that field is if you managed to fold the GEP into the MOVI. This would end up written in the .s fie as something like: MOVI $r0, date+8...

...eturn register $r4 JAL ... When I look at the text section (llvm-objdump -s output), I see this 0000 00c2 This is the correct MOVI opcode but the instead of the 0s, I should see the address of 'date' The ouput of llvm-objdump -r -t is this: RELOCATION RECORDS FOR [.rel.text]: 00000000 R_XXX_MOVI date (Note: correct relocation type) RELOCATION RECORDS FOR [.rel.eh_frame]: 0000001c R_XXX_NONE .text SYMBOL TABLE: 00000000 l df *ABS* 00000000 array.ll 00000000 l d .text 00000000 .text 00000000 g F .text 0000000e foo 00000000 g O .data 000000...