search for: arm_reloc_half

The llvm compiler can now generated movt/movw instructions to create 32-bit constants. Those new instructions use new relocations. Mach-o uses different numbering for relocations than ELF does. For mach-o, ARM_RELOC_PAIR=1 and ARM_RELOC_HALF=8. You need a newer linker that understands the new relocations. -Nick On Feb 20, 2012, at 5:20 AM, Harel Cain wrote: > Hi all, > > I'm trying to figure out a problem with relocation types 1 and 8 (as observed using otool -r on ARM/Thumb object files). Earlier, when I used LLVM 2....

Hi all, I'm trying to figure out a problem with relocation types 1 and 8 (as observed using otool -r on ARM/Thumb object files). Earlier, when I used LLVM 2.8 with llc to generate thumb (-march=thumb -mattr=+thumb2) assembly listings, then assemble those using the gcc of iPhone 4.2 SDK, there wasn't any problem. However starting with LLVM 2.9, the same toolchain emits slightly different

...--- next part -------------- diff --git a/include/llvm/Support/MachO.h b/include/llvm/Support/MachO.h index b2ac6b3..cb12902 100644 --- a/include/llvm/Support/MachO.h +++ b/include/llvm/Support/MachO.h @@ -402,6 +402,21 @@ namespace llvm { ARM_THUMB_32BIT_BRANCH = 7, // obsolete ARM_RELOC_HALF = 8, ARM_RELOC_HALF_SECTDIFF = 9, + + // Constant values for r_type field in an arm64 architecture + ARM64_RELOC_UNSIGNED = GENERIC_RELOC_VANILLA, // for pointers + ARM64_RELOC_SUBTRACTOR = 1, // must be followed by a ARM64_RELOC_UNSIGNED + ARM6...