This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: TLS redux
- From: "Joseph S. Myers" <joseph at codesourcery dot com>
- To: Carlos O'Donell <carlos at redhat dot com>
- Cc: Rich Felker <dalias at aerifal dot cx>, Jason Evans <jasone at canonware dot com>, Paul Pluzhnikov <ppluzhnikov at google dot com>, Andreas Schwab <schwab at linux-m68k dot org>, Roland McGrath <roland at hack dot frob dot com>, "GNU C. Library" <libc-alpha at sourceware dot org>, Will Newton <will dot newton at linaro dot org>
- Date: Thu, 30 Jan 2014 14:51:16 +0000
- Subject: Re: TLS redux
- Authentication-results: sourceware.org; auth=none
- References: <20140115022335 dot EB13174430 at topped-with-meat dot com> <Pine dot LNX dot 4 dot 64 dot 1401150520530 dot 14350 at digraph dot polyomino dot org dot uk> <CALoOobOyQxDaszErqoOkSdHsc7NestF7Pt9rS01aPzWZcnFZCQ at mail dot gmail dot com> <87r47tz5xd dot fsf at igel dot home> <CALoOobNZVFQ7z0uOgp6zAKMk7fmx03ua6S5E24UNgtVM3o=etQ at mail dot gmail dot com> <61CF7641-148C-4D7B-BE80-A1E3CC0AA498 at canonware dot com> <20140129012316 dot GM24286 at brightrain dot aerifal dot cx> <52E9E6FB dot 5010706 at redhat dot com>
On Thu, 30 Jan 2014, Carlos O'Donell wrote:
> I thought we ran into a similar bug for ARM and NEON?
https://sourceware.org/bugzilla/show_bug.cgi?id=15792
(this is distinct from the AArch64 bug someone referenced).
I believe the issue relates to:
(a) call-clobbered registers used for argument passing (including for
vector types etc.);
(b) other call-clobbered registers, if there are functions whose ABI has a
restricted clobber set that may be called through the PLT;
and that the places needing to handle saving and restoring are:
(i) _dl_runtime_resolve;
(ii) _dl_runtime_profile;
(iii) the TLS descriptors code in dl-tlsdesc.S.
Perhaps someone could confirm this and write up a description of how
architecture maintainers can determine if their architecture has any
issues in this regard, then send a message asking for architecture
maintainers to check and either confirm there are no issues or file a bug
describing the issues present? Then someone could track which
architectures have reported back.
--
Joseph S. Myers
joseph@codesourcery.com