Displaying 5 results from an estimated 5 matches for "r_address".
Did you mean:
__address
2014 Jun 10
4
[LLVMdev] MachO non-external X86_64_RELOC_UNSIGNED
.... All sections are
> parsed up into “atoms”. A location is an atom and an offset (within the
> atom). The expression for a fixup is a target atom and optional addend
> (e.g. &foo + 10).
>
> For X86_64_RELOC_UNSIGNED when r_extern=1, the location is the atom
> containing the r_address (offset in the section), and the expression is the
> atom corresponding to r_symbolnum plus the added that is the current
> content of the location. In the JIT case where you are trying to prepare a
> object file for execution, that boils down to adding the final address of
> the r_sym...
2016 Dec 07
2
Offset too large on scattered relocations
...if (FixupOffset > 0xffffff) {
char Buffer[32];
format("0x%x", FixupOffset).print(Buffer, sizeof(Buffer));
Asm.getContext().reportError(Fixup.getLoc(),
Twine("Section too large, can't encode "
"r_address (") + Buffer +
") into 24 bits of scattered "
"relocation entry.");
return false;
}
* Once we get here there seems to be nothing that can be done. Are there
ways of avoiding generation of scattered relocations? Iv...
2014 Jun 09
4
[LLVMdev] MachO non-external X86_64_RELOC_UNSIGNED
Hello everybody,
I would like some insights on the semantics of the X86_64_RELOC_UNSIGNED
relocation type. When r_extern=1, the semantics seem pretty clear:
Let x be a pointer to r_offset of appropriate size given by r_size, then
*x += addr_of_symbol(r_symbolnum)
However, when r_extern=0 the correct behavior is not clear. By analogy with
the above, I would have expected
*x +=
2016 Dec 07
0
Offset too large on scattered relocations
...ffff) {
> char Buffer[32];
> format("0x%x", FixupOffset).print(Buffer, sizeof(Buffer));
> Asm.getContext().reportError(Fixup.getLoc(),
> Twine("Section too large, can't encode "
> "r_address (") + Buffer +
> ") into 24 bits of scattered "
> "relocation entry.");
> return false;
> }
>
> * Once we get here there seems to be nothing that can be done. Are there ways of avoiding generatio...
2016 Dec 13
1
Offset too large on scattered relocations
...ffff) {
> char Buffer[32];
> format("0x%x", FixupOffset).print(Buffer, sizeof(Buffer));
> Asm.getContext().reportError(Fixup.getLoc(),
> Twine("Section too large, can't encode "
> "r_address (") + Buffer +
> ") into 24 bits of scattered "
> "relocation entry.");
> return false;
> }
>
> * Once we get here there seems to be nothing that can be done. Are there
> ways of avoiding gener...