Displaying 8 results from an estimated 8 matches for "reloff".
2012 Sep 27
1
[LLVMdev] CLang/LLVM SVN for today no longer works on OS X 10.7.4
...12
segname
vmaddr 0x0000000000000000
vmsize 0x0000000000000900
fileoff 464
filesize 2304
maxprot rwx
initprot rwx
nsects 3
flags (none)
Section
sectname __text
segname __TEXT
addr 0x0000000000000000
size 0x00000000000006b6
offset 464
align 2^4 (16)
reloff 2768
nreloc 9
type S_REGULAR
attributes PURE_INSTRUCTIONS SOME_INSTRUCTIONS
reserved1 0
reserved2 0
Section
sectname __compact_unwind
segname __LD
addr 0x00000000000006b6
size 0x00000000000000e0
offset 2182
align 2^0 (1)
reloff 2840
nreloc 7
type...
2012 Sep 26
0
[LLVMdev] CLang/LLVM SVN for today no longer works on OS X 10.7.4
Hi Kent,
My guess is you are getting some new bit of info in your object files and your ranlib(1) is older and doesn't know about it. If you can send me the .o file or the output of otool(1) with the -hlv options on your object file I can take a look.
Kev
P.S. you can find out the version of ranlib(1) you have by running strings(1) on it and grep(1)'ing for the string
2012 Sep 26
3
[LLVMdev] CLang/LLVM SVN for today no longer works on OS X 10.7.4
Ran into this today -- rebuilt the SVN Trunk for this morning of
LLVM+CLANG. Now every time my builds try and make a library from .o
files, ranlib complains about 'malformed object' files.
This is with OS X 10.7.4, and the binary tools from XCode 4.4.1
ld -v
@(#)PROGRAM:ld PROJECT:ld64-127.2
llvm version 3.0svn, from Apple Clang 3.0 (build 211.12)
ranlib doesn't tell you what
2011 Nov 23
0
[LLVMdev] (no subject)
...Finally I did…
$otool -X -s __DATA __objc_selrefs simple
00003034 00002fec 00002fe7 00002fd7 00002fcc
00003044 00002fc6 00002ff2
$ otool -l simple | grep selrefs -A20
sectname __objc_selrefs
segname __DATA
addr 0x00003034
size 0x00000018
offset 8244
align 2^2 (4)
reloff 0
nreloc 0
flags 0x10000005
reserved1 0
reserved2 0
Now, obviously these are where the selectors are, and sure enough when I
start walking the disass I find these addresses coming up.. but if I look
at address 0x3034 I don't see 00002fec or anything the like.., in fact,
using 0xED,...
2019 Jun 01
1
[Bug 13982] New: rsync calls exit() from signal handler
...7f7fff901d80, imm=imm at entry=true) at
/usr/src/libexec/ld.elf_so/symbol.c:391
#10 0x00007f7ef0400b34 in _rtld_relocate_plt_object (tp=<synthetic pointer>,
rela=0x77ea83c32e60, obj=0x77ea83fef400)
at /usr/src/libexec/ld.elf_so/arch/x86_64/mdreloc.c:310
#11 _rtld_bind (obj=0x77ea83fef400, reloff=<optimized out>) at
/usr/src/libexec/ld.elf_so/arch/x86_64/mdreloc.c:346
#12 0x00007f7ef04007cd in _rtld_bind_start () from /usr/libexec/ld.elf_so
#13 0x0000000000000202 in ?? ()
#14 0x00007f7fff901dd0 in ?? ()
#15 0x0000000000000000 in ?? ()
The backtrace suggests, and inspection of the cod...
2017 Sep 18
1
Do I need to modify the AddrLoc of LLD for ARC target?
...;> I implemented the MOD P for ARC:
>>>
>>> static void modifyARCAddrLoc(uint64_t &AddrLoc, const uint16_t EMachine,
>>> RelExpr Expr, uint32_t Type, uint64_t VMA,
>>> uint64_t OutSecOff, uint64_t RelOff) {
>>> if (EMachine != EM_ARC_COMPACT || EMachine != EM_ARC_COMPACT2 ||
>>> Expr != R_PC || Expr != R_GOT_PC) {
>>> return;
>>> }
>>>
>>> uint64_t M = 0;
>>> if (Type == R_ARC_32_PCREL || Type == R_ARC_PC32 || Type ==
&g...
2017 Sep 19
1
Do I need to modify the AddrLoc of LLD for ARC target?
...> static void modifyARCAddrLoc(uint64_t &AddrLoc, const uint16_t
>>>>> EMachine,
>>>>> RelExpr Expr, uint32_t Type, uint64_t
>>>>> VMA,
>>>>> uint64_t OutSecOff, uint64_t RelOff) {
>>>>> if (EMachine != EM_ARC_COMPACT || EMachine != EM_ARC_COMPACT2 ||
>>>>> Expr != R_PC || Expr != R_GOT_PC) {
>>>>> return;
>>>>> }
>>>>>
>>>>> uint64_t M = 0;
>>>>> if...
2017 Sep 14
4
Do I need to modify the AddrLoc of LLD for ARC target?
Hello Leslie,
I think we are going to need to know a bit more about the ELF ABI for
what looks like the ArcCompact before we can help you.
LLD's calculation of P (the place to be relocated) is as it is in the
generic ELF specification. The Rel.Offset corresponds to the ELF
r_offset field. This is covered by: "For a relocatable file, the value
is the byte offset from the beginning of the