[RTEMS Project] #3936: C++ thread-local storage broken on sparc64

RTEMS trac trac at rtems.org
Mon Apr 6 16:27:03 UTC 2020


#3936: C++ thread-local storage broken on sparc64
-----------------------------+---------------------------
 Reporter:  Sebastian Huber  |       Owner:  Gedare Bloom
     Type:  defect           |      Status:  assigned
 Priority:  normal           |   Milestone:  5.1
Component:  arch/sparc64     |     Version:  5
 Severity:  normal           |  Resolution:
 Keywords:                   |  Blocked By:
 Blocking:                   |
-----------------------------+---------------------------

Comment (by Joel Sherrill):

 I was disappointed in general when I looked for ABI definitions for TLS
 for various architectures. I think there is an Ulrich Drepper document
 describing a few (https://akkadia.org/drepper/tls.pdf) but I think it is
 undefined for a lot of architectures.

 Does GCC have a default mechanism? I couldn't find any hint of
 architecture specific TLS in the few secondary architectures I looked at.
 If there is a default way of calling a method for TLS info, it would be
 great. But at this point, I don't think TLS works from a GCC perspective
 on maybe half the architectures we support.

 sparc64 isn't a secondary gcc architecture so I am sure it works in GCC.
 Whether we want it around long term is another question entirely.

--
Ticket URL: <http://devel.rtems.org/ticket/3936#comment:2>
RTEMS Project <http://www.rtems.org/>
RTEMS Project


More information about the bugs mailing list