search for: image_rel_amd64_

Hi, Can anyone explain in lib/ExecutionEngine/RuntimeDyld/Targets/ the header files included for different architectures like RuntimeDyldCOFFX86_64.h or RuntimeDyldCOFFI386.h etc, what is the connection of these files for relocation and linking as the linking and relocation for diff architecture is done in RuntimeDyldELF.cpp, RuntimeDyldCOFF.cpp and it doesn't use any function from these

...derived form of the class that processes the relocation > records when dynamically loading JITed code in LLVM - mainly implementing > the two different forms of symbol entries that refer to the relocations - > i386 uses COFF::IMAGE_REL_I386_*, in x86_64 the relocation types are > COFF::IMAGE_REL_AMD64_*. > > Conceptually, they do the same thing, it's the details of exactly how and > where the relocation ends up and how it's recorded by the linker that > differs. > > Theoretically, one could probably construct a loadable file that doesn't > care what architecture i...

...en dynamically loading JITed code in LLVM - mainly implementing >>>>>>> the two different forms of symbol entries that refer to the relocations - >>>>>>> i386 uses COFF::IMAGE_REL_I386_*, in x86_64 the relocation types are >>>>>>> COFF::IMAGE_REL_AMD64_*. >>>>>>> >>>>>>> Conceptually, they do the same thing, it's the details of exactly >>>>>>> how and where the relocation ends up and how it's recorded by the linker >>>>>>> that differs. >>>>>...

...ITed code in LLVM - mainly implementing >>>>>>>>> the two different forms of symbol entries that refer to the relocations - >>>>>>>>> i386 uses COFF::IMAGE_REL_I386_*, in x86_64 the relocation types are >>>>>>>>> COFF::IMAGE_REL_AMD64_*. >>>>>>>>> >>>>>>>>> Conceptually, they do the same thing, it's the details of exactly >>>>>>>>> how and where the relocation ends up and how it's recorded by the linker >>>>>>>>> th...