https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113874
--- Comment #18 from Florian Weimer <fw at gcc dot gnu.org> --- (In reply to Richard Biener from comment #16) > I do wonder why __tls_get_addr would have to call the overloaded malloc, can > we just not force-bind it to the glibc local malloc (and make sure that's > compiled with -mgeneral-regs-only)? Using the glibc malloc just for some small TLS allocation is rather wasteful because of its (mostly) per-thread data structures. Allocating from the main arena potentially clashes with brk usage from the replacement malloc. We'd need an alternative memory allocator (in addition to replacement string functions), but that is known to break Thread Sanitizer and Leak Sanitizer.
