|author||Rich Felker <firstname.lastname@example.org>||2014-04-12 00:16:19 -0400|
|committer||Rich Felker <email@example.com>||2014-04-12 00:16:19 -0400|
use hidden visibility rather than protected for syscall internals
the use of visibility at all is purely an optimization to avoid the need for the caller to load the GOT register or similar to prepare for a call via the PLT. there is no reason for these symbols to be externally visible, so hidden works just as well as protected, and using protected visibility is undesirable due to toolchain bugs and the lack of testing it receives. in particular, GCC's microblaze target is known to generate symbolic relocations in the GOT for functions with protected visibility. this in turn results in a dynamic linker which crashes under any nontrivial usage that requires making a syscall before symbolic relocations are processed.
Diffstat (limited to 'arch')
0 files changed, 0 insertions, 0 deletions