Lines Matching refs:glibc
212 memory in the static TLS block. glibc reserves a kilobyte or two (`TLS_STATIC_SURPLUS`) with the
216 * web search: [`"dlopen: cannot load any more object with static TLS"`][glibc-static-tls-error]
228 [glibc-static-tls-error]: https://www.google.com/search?q=%22dlopen:+cannot+load+any+more+object+wi…
421 The metadata variables are local symbols in glibc's `libpthread.so` symbol table (but not its
436 these sorts of problems with glibc's libpthread?)
536 implementations (glibc, musl, FreeBSD) vary in their level of respect for TLS alignment. It looks
545 it's feasible. musl's function is AS-safe, but glibc's isn't (or wasn't). Google had a patch to make
546 glibc AS-safe back in 2012-2013. See:
547 * https://sourceware.org/glibc/wiki/TLSandSignals
840 * https://sourceware.org/glibc/wiki/ThreadPropertiesAPI
847 * It looks like glibc's ld.so re-relocates itself after loading a program, so a program's symbols