search for: r_word0

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 PM, Nick Kledzik...

> On Dec 6, 2016, at 5:09 PM, Rob Dalvik <rob.dalvik at gmail.com> wrote: > > CCing Nick Kledzik as I posed this question on IRC and Tim Northover suggested you as a good resource for this. > > I came across an error due to a scattered relocation offset being larger than 2**24 and I was hoping to find more information on scattered relocations. These are MachO specific, and

CCing Nick Kledzik as I posed this question on IRC and Tim Northover suggested you as a good resource for this. I came across an error due to a scattered relocation offset being larger than 2**24 and 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

...>getSectionAddress(&SymSD); + } + if (IsPCRel) + FixedValue -= Writer->getSectionAddress(Fragment->getParent()); + + // The type is determined by the fixup kind. + Type = RelocType; + } + + // struct relocation_info (8 bytes) + MachO::any_relocation_info MRE; + MRE.r_word0 = FixupOffset; + MRE.r_word1 = ((Index << 0) | (IsPCRel << 24) | (Log2Size << 25) | + (IsExtern << 27) | (Type << 28)); + + Writer->addRelocation(Fragment->getParent(), MRE); + + if (IsExtern) + FixedValue = 0; +} + +MCObjectWriter *llvm::cr...