[Bug 2749] Dynamic modules need visibility cleanups

[bugzilla-daemon at freedesktop.org]

Please do not reply to this email: if you want to comment on the bug, go to    
       
the URL shown below and enter yourcomments there.     
   
https://bugs.freedesktop.org/show_bug.cgi?id=2749          
     




------- Additional Comments From ajax at nwnk.net  2005-03-16 14:36 -------
very cool, didn't know about -xldscope.  it and the tags don't seem to be in the
Forte 7 C developers manual:

http://docs.sun.com/source/816-2454/index.html

the only problem with using the map file is it's after code generation has been
done.  the symbol won't show up in the dynamic symbol table but the call
prologue for it will still be the same as if it were default visibility, so you
still hit the PLT/GOT indirection overhead.  better than nothing.

i'd probably pursue a hybrid approach of adding both static and EXPORTED tags,
with EXPORTED #defined to nothing for compilers with no visibility control and
to __global or equivalent for good compilers.  this provides an easy transition
path, because when we detect a good compiler we can just add the option to
CFLAGS and win.  this is the approach i used in Mesa and it works well.          
     
     
--           
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email         
     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.