--- Comment #6 from iains at gcc dot gnu dot org 2010-06-11 08:37 ---
closing as fixed by r160457 (trunk) and r160526 (4.5 release branch)
--
iains at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #5 from ktietz at gcc dot gnu dot org 2010-01-23 10:35 ---
Yes, I can confirm this issue, but want to investigate where the underlying
issue really comes from. The interesting issue I found is, that if a
TLS-variable isn't assigned, the values of the addresses in different
--- Comment #1 from jos dot de_laender at telenet dot be 2010-01-21 15:42
---
Created an attachment (id=19681)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19681action=view)
The test.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42829
--- Comment #2 from pinskia at gcc dot gnu dot org 2010-01-21 19:48 ---
Oh this test should pass no matter what really as TLS is emulated on mingw via
functions which call pthreads.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42829
--- Comment #3 from jakub at gcc dot gnu dot org 2010-01-21 20:37 ---
Yeah, the test is certainly fine, if it sporadically fails, there are issues
with the mingw TLS or thread implementation (or both).
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42829
--- Comment #4 from jos dot de_laender at telenet dot be 2010-01-21 22:14
---
Your call.
I *don't* think it's fine.
Even if there *is* TLS, it can fail due to the -O2 optimizing.
(it doesn't detect the referring via ).
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42829
