search for: r_aarch64_call26

Displaying 4 results from an estimated 4 matches for "r_aarch64_call26".

2015 May 06
2
[LLVMdev] [lld] Wrong references for C++ COMDAT groups
...ction relocation with same offset, but for a different text segments (the exception handler stub create by clang): Relocation section '.rela.text' at offset 0xed8 contains 2 entries: Offset Info Type Sym. Value Sym. Name + Addend 000000000010 00480000011b R_AARCH64_CALL26 0000000000000000 _ZNSt9exceptionD2Ev + 0 000000000020 004d0000011a R_AARCH64_JUMP26 0000000000000000 _ZdlPv + 0 Relocation section '.rela.text' at offset 0xf08 contains 2 entries: Offset Info Type Sym. Value Sym. Name + Addend 000000000010 00480000011b...
2015 May 07
2
[LLVMdev] [lld] Wrong references for C++ COMDAT groups
...r a > different text segments (the exception handler stub create by clang): > > Relocation section '.rela.text' at offset 0xed8 contains 2 entries: > Offset Info Type Sym. Value Sym. Name + Addend > 000000000010 00480000011b R_AARCH64_CALL26 0000000000000000 _ZNSt9exceptionD2Ev + 0 > 000000000020 004d0000011a R_AARCH64_JUMP26 0000000000000000 _ZdlPv + 0 > > Relocation section '.rela.text' at offset 0xf08 contains 2 entries: > Offset Info Type Sym. Value Sym. Name + A...
2014 Jul 28
2
[LLVMdev] [lld] question on ELF section formating
...E5, 03, 00, AA, E1, 03, 40, F9, E2, 23, 00, 91, E6, 03, 00, 91, A0, 00, 00, 58, C3, 00, 00, 58, E4, 00, 00, 58, 00, 00, 00, 94, 00, 00, 00, 94 ] alignment: 2^3 section-name: .text references: - kind: R_AARCH64_CALL26 offset: 40 target: __plt___libc_start_main - kind: R_AARCH64_CALL26 offset: 44 target: __plt_abort - kind: in-group offset: 0 target: L030 - kind:...
2014 Jun 20
2
[LLVMdev] [AArch64] Question about far call
Hi, For the following code: void foo (); int main () {foo();} llvm emits "bl foo" Then I set foo at a far address in linking: aarch64-linux-gnu-gcc -Wl,--defsym=foo=0x80000000 a.o -o a.exe I got an error from ld: a.c:(.text+0x8): relocation truncated to fit: R_AARCH64_CALL26 against symbol `foo' define in *ABS* section in a.exe The question is: do I miss some options or pragmas during compilation ? Should I expect llvm to emit the following code? movz x8, #:abs_g3:foo movk x8, #:abs_g2_nc:foo movk...