search for: recordarmscatteredhalfreloc

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

Offset too large on scattered relocations
2016 Dec 07
2
Offset too large on scattered relocations
...rmation on scattered relocations. These are MachO specific, and Ive not been able to find any documentation on them outside of source code. I have a couple of immediate questions, but any info would be appreciated. * Should a check be added to ARMMachObjectWriter::RecordARMScatteredRelocation and RecordARMScatteredHalfRelocation to ensure that 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 ||...
Offset too large on scattered relocations
2016 Dec 07
0
Offset too large on scattered relocations
...relocations. These are MachO specific, and Ive not been able to find any documentation on them outside of source code. > > I have a couple of immediate questions, but any info would be appreciated. > > * Should a check be added to ARMMachObjectWriter::RecordARMScatteredRelocation and RecordARMScatteredHalfRelocation to ensure that 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::GENE...
Offset too large on scattered relocations
2016 Dec 13
1
Offset too large on scattered relocations
...ions. These are MachO specific, and Ive not been able to find any > documentation on them outside of source code. > > I have a couple of immediate questions, but any info would be appreciated. > > * Should a check be added to ARMMachObjectWriter::RecordARMScatteredRelocation > and RecordARMScatteredHalfRelocation to ensure that 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 == Mac...