Re: effect of -fPIC on code speed

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Andrew Haley <aph@xxxxxxxxxx> 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 of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux