public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libc/16990] New: ARM: Concurrent TLS descriptor resolution fails
@ 2014-05-27  9:34 will.newton at gmail dot com
  2014-05-27  9:40 ` [Bug libc/16990] " cvs-commit at gcc dot gnu.org
                   ` (3 more replies)
  0 siblings, 4 replies; 5+ messages in thread
From: will.newton at gmail dot com @ 2014-05-27  9:34 UTC (permalink / raw)
  To: glibc-bugs

https://sourceware.org/bugzilla/show_bug.cgi?id=16990

            Bug ID: 16990
           Summary: ARM: Concurrent TLS descriptor resolution fails
           Product: glibc
           Version: 2.18
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
          Assignee: unassigned at sourceware dot org
          Reporter: will.newton at gmail dot com
                CC: drepper.fsp at gmail dot com
              Host: arm

When building glibc with CFLAGS="-mtls-dialect=gnu2 -O2 -g" nptl/tst-tls3
fails. This is caused by concurrent TLS descriptor resolution occuring and a
bug in the code to handle this situation.

_dl_tlsdesc_resolve_hold restores r2 as it assumes that it is being called in
the same circumstances as _dl_tlsdesc_lazy_resolver, but it is not. The lazy
resolver is called from a stub that pushes r2 whereas _dl_tlsdesc_resolve_hold
is called from the TLS descriptor trampoline which does not.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2014-06-26 13:50 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-05-27  9:34 [Bug libc/16990] New: ARM: Concurrent TLS descriptor resolution fails will.newton at gmail dot com
2014-05-27  9:40 ` [Bug libc/16990] " cvs-commit at gcc dot gnu.org
2014-05-27  9:40 ` will.newton at gmail dot com
2014-05-27  9:41 ` will.newton at gmail dot com
2014-06-26 13:50 ` fweimer at redhat dot com

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).