This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug ipa/80258] On x86_64 with -fPIC, accesses to TLS can see the wrong thread's TLS


https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80258

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org

--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
This is not a bug, that is how TLS is designed.  You shouldn't change threads
in the middle of a function.  If you do, you shouldn't use TLS, but something
different; basically you are implementing your own threading library then and
you are responsible for arranging that it works.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]