Displaying 3 results from an estimated 3 matches for "recordarmscatteredrelocation".
2016 Dec 13
1
Offset too large on scattered relocations
Thanks for the response Nick,
Do you think there is value in adding the check for FixupOffset > 0xffffff
into the ARM backend? The lack of that seems like it could silently record
incorrect offsets from the assignment later in
RecordARMScatteredRelocation():
MRE.r_word0 = ((FixupOffset << 0) |
(Type << 24) |
(MovtBit << 28) |
(ThumbBit << 29) |
(IsPCRel << 30) |
MachO::R_SCATTERED);
Rob
On Tue, Dec 6, 2016 at 8:38...
2016 Dec 07
2
Offset too large on scattered relocations
...nd I was hoping to find more information 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 == Mach...
2016 Dec 07
0
Offset too large on scattered relocations
...nd more information 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...