freebsd-nq/lib/libc/stdlib/Symbol.map

133 lines
1.3 KiB
Plaintext
Raw Normal View History

/*
* $FreeBSD$
*/
FBSD_1.0 {
_Exit;
a64l;
abort;
abs;
atexit;
__cxa_atexit;
__cxa_finalize;
atof;
atoi;
atol;
atoll;
bsearch;
div;
__isthreaded;
exit;
getenv;
opterr;
optind;
optopt;
optreset;
optarg;
getopt;
getopt_long;
getopt_long_only;
suboptarg;
getsubopt;
grantpt;
ptsname;
unlockpt;
hcreate;
hdestroy;
hsearch;
heapsort;
imaxabs;
imaxdiv;
insque;
l64a;
l64a_r;
labs;
ldiv;
llabs;
lldiv;
lsearch;
lfind;
mergesort;
putenv;
qsort_r;
qsort;
radixsort;
sradixsort;
rand_r;
rand;
srand;
sranddev;
srandom;
srandomdev;
initstate;
setstate;
random;
reallocf;
realpath;
remque;
setenv;
unsetenv;
strfmon;
strtoimax;
strtol;
strtoll;
strtonum;
strtoq;
strtoul;
strtoull;
strtoumax;
strtouq;
system;
tdelete;
tfind;
tsearch;
twalk;
};
FBSD_1.3 {
2012-01-08 12:04:22 +00:00
at_quick_exit;
atof_l;
atoi_l;
atol_l;
atoll_l;
quick_exit;
strtod_l;
strtof_l;
strtoimax_l;
2012-01-08 12:04:22 +00:00
strtol_l;
strtold_l;
2012-01-08 12:04:22 +00:00
strtoll_l;
strtoq_l;
strtoul_l;
strtoull_l;
strtoumax_l;
strtouq_l;
};
FBSD_1.4 {
atexit_b;
bsearch_b;
heapsort_b;
mergesort_b;
qsort_b;
hcreate_r;
hdestroy_r;
hsearch_r;
reallocarray;
};
Add __cxa_thread_atexit(3) API implementation. This is the backing feature to implement C++11 thread storage duration specified by the thread_local keyword. A destructor for given thread-local object is registered to be executed at the thread termination time using __cxa_thread_atexit(). Libc calls the __cxa_thread_calls_dtors() during exit(3), before finalizers and atexit functions, and libthr calls the function at the thread termination time, after the stack unwinding and thread-specific key destruction. There are several uncertainties in the API which lacks a formal specification. Among them: - is it allowed to register destructors during destructing; we allow, but limiting the nesting level. If too many iterations detected, a diagnostic is issued to stderr and thread forcibly terminates for now. - how to handle destructors which belong to an unloading dso; for now, we ignore destructor calls for such entries, and issue a diagnostic. Linux does prevent dso unload until all threads with destructors from the dso terminated. It is supposed that the diagnostics allow to detect real-world applications relying on the above details and possibly adjust our implementation. Right now the choices were to provide the slim API (but that rarely stands the practice test). Tests are added to check generic functionality and to specify some of the above implementation choices. Submitted by: Mahdi Mokhtari <mokhi64_gmail.com> Reviewed by: theraven Discussed with: dim (detection of -std=c++11 supoort for tests) Sponsored by: The FreeBSD Foundation (my involvement) MFC after: 2 weeks Differential revisions: https://reviews.freebsd.org/D7224, https://reviews.freebsd.org/D7427
2016-08-06 13:32:40 +00:00
FBSD_1.5 {
__cxa_thread_atexit;
__cxa_thread_atexit_impl;
abort_handler_s;
ignore_handler_s;
set_constraint_handler_s;
Add __cxa_thread_atexit(3) API implementation. This is the backing feature to implement C++11 thread storage duration specified by the thread_local keyword. A destructor for given thread-local object is registered to be executed at the thread termination time using __cxa_thread_atexit(). Libc calls the __cxa_thread_calls_dtors() during exit(3), before finalizers and atexit functions, and libthr calls the function at the thread termination time, after the stack unwinding and thread-specific key destruction. There are several uncertainties in the API which lacks a formal specification. Among them: - is it allowed to register destructors during destructing; we allow, but limiting the nesting level. If too many iterations detected, a diagnostic is issued to stderr and thread forcibly terminates for now. - how to handle destructors which belong to an unloading dso; for now, we ignore destructor calls for such entries, and issue a diagnostic. Linux does prevent dso unload until all threads with destructors from the dso terminated. It is supposed that the diagnostics allow to detect real-world applications relying on the above details and possibly adjust our implementation. Right now the choices were to provide the slim API (but that rarely stands the practice test). Tests are added to check generic functionality and to specify some of the above implementation choices. Submitted by: Mahdi Mokhtari <mokhi64_gmail.com> Reviewed by: theraven Discussed with: dim (detection of -std=c++11 supoort for tests) Sponsored by: The FreeBSD Foundation (my involvement) MFC after: 2 weeks Differential revisions: https://reviews.freebsd.org/D7224, https://reviews.freebsd.org/D7427
2016-08-06 13:32:40 +00:00
};
FBSDprivate_1.0 {
__system;
_system;
Fix known issues which blow up the process after dlopen("libthr.so") (or loading a dso linked to libthr.so into process which was not linked against threading library). - Remove libthr interposers of the libc functions, including __error(). Instead, functions calls are indirected through the interposing table, similar to how pthread stubs in libc are already done. Libc by default points either to syscall trampolines or to existing libc implementations. On libthr load, libthr rewrites the pointers to the cancellable implementations already in libthr. The interposition table is separate from pthreads stubs indirection table to not pull pthreads stubs into static binaries. - Postpone the malloc(3) internal mutexes initialization until libthr is loaded. This avoids recursion between calloc(3) and static pthread_mutex_t initialization. - Reinstall signal handlers with wrapper on libthr load. The _rtld_is_dlopened(3) is used to avoid useless calls to sigaction(2) when libthr is statically referenced from the main binary. In the process, fix openat(2), swapcontext(2) and setcontext(2) interposing. The libc symbols were exported at different versions than libthr interposers. Export both libc and libthr versions from libc now, with default set to the higher version from libthr. Remove unused and disconnected swapcontext(3) userspace implementation from libc/gen. No objections from: deischen Tested by: pho, antoine (exp-run) (previous versions) Sponsored by: The FreeBSD Foundation MFC after: 1 week
2015-01-03 18:38:46 +00:00
__libc_system;
Add __cxa_thread_atexit(3) API implementation. This is the backing feature to implement C++11 thread storage duration specified by the thread_local keyword. A destructor for given thread-local object is registered to be executed at the thread termination time using __cxa_thread_atexit(). Libc calls the __cxa_thread_calls_dtors() during exit(3), before finalizers and atexit functions, and libthr calls the function at the thread termination time, after the stack unwinding and thread-specific key destruction. There are several uncertainties in the API which lacks a formal specification. Among them: - is it allowed to register destructors during destructing; we allow, but limiting the nesting level. If too many iterations detected, a diagnostic is issued to stderr and thread forcibly terminates for now. - how to handle destructors which belong to an unloading dso; for now, we ignore destructor calls for such entries, and issue a diagnostic. Linux does prevent dso unload until all threads with destructors from the dso terminated. It is supposed that the diagnostics allow to detect real-world applications relying on the above details and possibly adjust our implementation. Right now the choices were to provide the slim API (but that rarely stands the practice test). Tests are added to check generic functionality and to specify some of the above implementation choices. Submitted by: Mahdi Mokhtari <mokhi64_gmail.com> Reviewed by: theraven Discussed with: dim (detection of -std=c++11 supoort for tests) Sponsored by: The FreeBSD Foundation (my involvement) MFC after: 2 weeks Differential revisions: https://reviews.freebsd.org/D7224, https://reviews.freebsd.org/D7427
2016-08-06 13:32:40 +00:00
__cxa_thread_call_dtors;
};