[krbdev.mit.edu #3316] evaluate use of ELF symbol visibility pragmas for smaller code, GOT, PLT

[Ken Raeburn via RT]

On Dec 29, 2005, at 21:31, Sam Hartman via RT wrote:
> O, sorry, I meant to imply that we should set things up so all our
> symbol properties come from one place.  I.E. it is impossible to get
> it wrong because there is only one place the data lives so it cannot
> be inconsistent with anything.

Ah, I see.  That might be tricky, since one is markers in a header  
file related only by position to the function declarations, and the  
other is a list of symbols, but perhaps something can be worked up,  
maybe parsing the header file to generate the initial symbol list.