This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/16291] feature request: provide simpler ways to compute stack and tls boundaries
- From: "carlos at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Thu, 15 Feb 2018 21:56:42 +0000
- Subject: [Bug libc/16291] feature request: provide simpler ways to compute stack and tls boundaries
- Auto-submitted: auto-generated
- References: <bug-16291-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=16291
--- Comment #53 from Carlos O'Donell <carlos at redhat dot com> ---
I should note that Rust has similar requirements here, I was talking to Josh
Stone about this because recent glibc changes made it harder for Rust to know
the exact stack boundaries.
Rust wants to know about the stack boundaries for every thread because it wants
to handle the cases where the thread is getting close to running out of memory.
In the past the guard size was part of the stack, and after the fixes for bug
22637 it is not, so all low-level code which needed to know this internal
detail now needs to adjust for this (like calling __pthread_get_minstack, which
Rust does).
--
You are receiving this mail because:
You are on the CC list for the bug.