This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: effect of -fPIC on code speed


Andrew Haley <aph@redhat.com> writes:
> It's actually part of the C standard: there may only be one definition
> of any symbol, whether that symbol refers to a function or to data.  So,
> for every visible symbol X in a program, &X must be the same, no matter
> who is asking.  All manner of things break without this.

Are symbols in a shared object loaded with e.g. dlopen "visible" (in the
sense of being unified with symbols in the executable, not visible via a
special lookup like dlsym)?

-Miles

-- 
Freebooter, n. A conqueror in a small way of business, whose annexations lack
of the sanctifying merit of magnitude.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]