Amd64 relocation R_X86_64_32S in a static lib

[Niels Möller]

Philip Guenther <guenther at gmail.com> writes:

>> That's bad.  But then why not allow R_X86_64_32S too?
>
> Because there's no guarantee that the target is within 2GB, as the 
> reference may resolve to the symbol in a different shared object which is 
> too far away.

Can you use ELF visibility to provide the needed guarantee that it will
never resolve to a symbol in a different shared object?

I think references *within* a shared object is an important and common
case, worthy of some optimization.

Regards,
/Niels

-- 
Niels Möller. PGP-encrypted email is preferred. Keyid C0B98E26.
Internet email is subject to wholesale government surveillance.