search for: getorcreatelinkerdefinedatom

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

2015 Feb 23
2
[LLVMdev] [lld] Undefined symbols postprocessing
...al linker symbols. I propose two things. 1. Provide a hook as per what Shankar suggested for the resolver. User references to linker defined symbols such as _GLOBAL_OFFSET_TABLE_ get created and possibly deadstripped here. The linking context owns the atom. 2. The ELFLinkingContext gains <Atom *getOrCreateLinkerDefinedAtom(StringRef);>. This can be used in passes to get the symbols. The hook in (1) would call this to create the atoms. This gives a single place where linker defined atoms are actually created, and allows correct deadstripping and object file references without doing multiple resolver passes. - Mic...
2015 Feb 25
2
[LLVMdev] [lld] Undefined symbols postprocessing
...hings. > > 1. Provide a hook as per what Shankar suggested for the resolver. User > references to linker defined symbols such as _GLOBAL_OFFSET_TABLE_ get > created and possibly deadstripped here. The linking context owns the > atom. > 2. The ELFLinkingContext gains <Atom > *getOrCreateLinkerDefinedAtom(StringRef);>. This can be used in passes > to get the symbols. The hook in (1) would call this to create the > atoms. > > This gives a single place where linker defined atoms are actually > created, and allows correct deadstripping and object file references > without doing mul...
2015 Feb 19
4
[LLVMdev] [lld] Undefined symbols postprocessing
+ Nick On 2/19/2015 9:00 AM, Shankar Easwaran wrote: > On 2/19/2015 3:58 AM, Denis Protivensky wrote: >> Joerg: >>> I propose to add the ability to ignore undefined symbols during initial >>> resolution, and then postprocess only those undefines for the second >>> time >>> after the pass manager execution. >> Do you want to do that before or