This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/5649] New: too many symbols exported from libc
- From: "bruno at clisp dot org" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: 19 Jan 2008 00:37:08 -0000
- Subject: [Bug libc/5649] New: too many symbols exported from libc
- Reply-to: sourceware-bugzilla at sourceware dot org
Ulrich Drepper once said that the number of symbols exported from libc should
not be high without need, the reason being the size of the ELF hash table
and the startup time of executables.
Here is a list of symbols that are
1) exported from libc.so (in glibc-2.3.6 at least),
2) not declared in any public header file (I checked glibc-2.3.6 and -2.6.1),
3) are not Linux system calls.
Each of them is a candidate for trimming - or for making available in a
public include file if the programmer is intended to use it.
chflags
fchflags
fcrypt
h_errlist
h_nerr
iruserok
iruserok_af
key_setnet
mallwatch
moncontrol
nis_clone_directory
nis_clone_result
nis_free_directory
nis_free_object
nis_free_request
nis_read_obj
nis_write_obj
passwd2des
pthread_mutexattr_getkind_np
pthread_mutexattr_setkind_np
re_max_failures
readColdStartFile
registerrpc
res_gethostbyaddr
res_gethostbyname
res_gethostbyname2
res_send_setqhook
res_send_setrhook
rexecoptions
ruserpass
sstk
svcauthdes_stats
svcfd_create
svcudp_enablecache
svcunixfd_create
sys_sigabbrev
tr_break
writeColdStartFile
xdecrypt
xdr_accepted_reply
xdr_authdes_cred
xdr_authdes_verf
xdr_rejected_reply
xencrypt
yp_maplist
--
Summary: too many symbols exported from libc
Product: glibc
Version: 2.4
Status: NEW
Severity: normal
Priority: P2
Component: libc
AssignedTo: drepper at redhat dot com
ReportedBy: bruno at clisp dot org
CC: glibc-bugs at sources dot redhat dot com
GCC build triplet: i586-unknown-linux-gnu
GCC host triplet: i586-unknown-linux-gnu
GCC target triplet: i586-unknown-linux-gnu
http://sourceware.org/bugzilla/show_bug.cgi?id=5649
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.