Displaying 3 results from an estimated 3 matches for "n_no_dead_strip".
2012 Nov 12
1
[LLVMdev] lld deadstrip atoms
...tribute(used)__ which could be set for each symbol, but this is only a compiler hint. The information is not passed in the symbol table. If this is not passed in the symbol table to the linker, why is it in the DefinedAtom ?
> In mach-o it *is* passed on to the linker by the compiler. It is the N_NO_DEAD_STRIP bit in the n_desc field of the nlist struct. Are you saying that that information is not recorded in ELF .o files?
On ELF x86_64, I dont see the information being passed. Is clang
planning to add this support ?
Thanks
Shankar Easwaran
--
Qualcomm Innovation Center, Inc. is a member of Code Au...
2012 Nov 12
0
[LLVMdev] lld deadstrip atoms
...__attribute(used)__ which could be set for each symbol, but this is only a compiler hint. The information is not passed in the symbol table. If this is not passed in the symbol table to the linker, why is it in the DefinedAtom ?
In mach-o it *is* passed on to the linker by the compiler. It is the N_NO_DEAD_STRIP bit in the n_desc field of the nlist struct. Are you saying that that information is not recorded in ELF .o files?
-Nick
2012 Nov 09
2
[LLVMdev] lld deadstrip atoms
Hi Nick,
Dead stripping optimization needs a way to setup the roots which are
live. The current code in Resolver does it by
1) setting all the global defined atoms to be the live set when building
shared libraries (_options.allGlobalsAreDeadStripRoots)
2) Or, uses a list of names that are dead strip roots (other types)
Question:-
***********
How are the dead strip root names supposed to be