search for: generic_reloc_local_sectdiff

Displaying 3 results from an estimated 3 matches for "generic_reloc_local_sectdiff".

2016 Dec 07
2
Offset too large on scattered relocations
...at FixupOffset is within bounds? I see a check in the x86 back end that does precisely this and was curious why a similar check was not in place for ARM: // Relocations are written out in reverse order, so the PAIR comes first. if (Type == MachO::GENERIC_RELOC_SECTDIFF || Type == MachO::GENERIC_RELOC_LOCAL_SECTDIFF) { // If the offset is too large to fit in a scattered relocation, // we're hosed. It's an unfortunate limitation of the MachO format. if (FixupOffset > 0xffffff) { char Buffer[32]; format("0x%x", FixupOffset).print(Buffer, sizeof(Buffer)); Asm.get...
2016 Dec 07
0
Offset too large on scattered relocations
...s? > > I see a check in the x86 back end that does precisely this and was curious why a similar check was not in place for ARM: > > // Relocations are written out in reverse order, so the PAIR comes first. > if (Type == MachO::GENERIC_RELOC_SECTDIFF || > Type == MachO::GENERIC_RELOC_LOCAL_SECTDIFF) { > // If the offset is too large to fit in a scattered relocation, > // we're hosed. It's an unfortunate limitation of the MachO format. > if (FixupOffset > 0xffffff) { > char Buffer[32]; > format("0x%x", FixupOffset).print(Buffer, sizeo...
2016 Dec 13
1
Offset too large on scattered relocations
...> > I see a check in the x86 back end that does precisely this and was curious > why a similar check was not in place for ARM: > > // Relocations are written out in reverse order, so the PAIR comes first. > if (Type == MachO::GENERIC_RELOC_SECTDIFF || > Type == MachO::GENERIC_RELOC_LOCAL_SECTDIFF) { > // If the offset is too large to fit in a scattered relocation, > // we're hosed. It's an unfortunate limitation of the MachO format. > if (FixupOffset > 0xffffff) { > char Buffer[32]; > format("0x%x", FixupOffset).print(Buffer, sizeo...