effect of -fPIC on code speed

Miles Bader miles@gnu.org
Mon Sep 20 18:21:00 GMT 2010

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)?


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

More information about the Gcc-help mailing list