https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91628
Florian Weimer <fw at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fw at gcc dot gnu.org
--- Comment #2 from Florian Weimer <fw at gcc dot gnu.org> ---
(In reply to Carlos O'Donell from comment #1)
> Note that is also the case for Rust which uses
> __pthread_get_minstack@@GLIBC_PRIVATE, and this has prevented us from doing
> valid and meaningful cleanup of the libpthread internals to remove this
> function.
The use of __pthread_get_minstack@@GLIBC_PRIVATE in Rust was safe last time I
checked, treating a missing function as indicating that glibc will not place
the TCB on the stack. The use in OpenJDK follows this pattern too. If we
change TCB allocation not to use the stack anymore, we can remove the function
at the same time, and Rust and OpenJDK will still do the right thing.
(This is just an aside here, of course.)
