[Bug sanitizer/78294] -fsanitize=thread broken

2016-11-15 Thread trippels at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78294 --- Comment #12 from Markus Trippelsdorf --- Created attachment 40050 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=40050=edit unreduced testcase Indeed it look like gcc simply ignores the attribute: g++ -fPIC -O2 -g -c tsan_rtl.ii vs.

[Bug sanitizer/78294] -fsanitize=thread broken

2016-11-15 Thread trippels at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78294 Markus Trippelsdorf changed: What|Removed |Added Status|RESOLVED|REOPENED Last reconfirmed|

[Bug sanitizer/78294] -fsanitize=thread broken

2016-11-12 Thread trippels at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78294 --- Comment #10 from Markus Trippelsdorf --- It might make sense to add -fuse-ld=bfd to the AM_CXXFLAGS for now. (lld is also broken.)

[Bug sanitizer/78294] -fsanitize=thread broken

2016-11-11 Thread trippels at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78294 Markus Trippelsdorf changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug sanitizer/78294] -fsanitize=thread broken

2016-11-11 Thread trippels at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78294 --- Comment #8 from Markus Trippelsdorf --- I've opened https://sourceware.org/bugzilla/show_bug.cgi?id=20805. It would be good if someone could come up with a small testcase.

[Bug sanitizer/78294] -fsanitize=thread broken

2016-11-11 Thread trippels at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78294 --- Comment #7 from Markus Trippelsdorf --- Disassembly of libtsan.so.0.0.0: 0006efd0 <_ZN6__tsan10InitializeEPNS_11ThreadStateE>: if (is_initialized)

[Bug sanitizer/78294] -fsanitize=thread broken

2016-11-11 Thread trippels at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78294 --- Comment #6 from Markus Trippelsdorf --- OK, it looks like a ld.gold bug. I normally always use ld.gold on my system. However if I build gcc with ld.bfd then everything works fine.

[Bug sanitizer/78294] -fsanitize=thread broken

2016-11-11 Thread dvyukov at google dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78294 --- Comment #5 from Dmitry Vyukov --- Markus, how do you configure and build gcc? Is there anything special? Our tls accesses should not go through __tls_get_addr because we use initial-exec attribute. __tls_get_addr vs indirect access through

[Bug sanitizer/78294] -fsanitize=thread broken

2016-11-11 Thread trippels at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78294 --- Comment #4 from Markus Trippelsdorf --- (gdb) up #3 __tsan::Initialize (thr=thr@entry=0x76277780) at ../../../../gcc/libsanitizer/tsan/tsan_rtl.cc:331 331 ScopedIgnoreInterceptors ignore; (gdb) disass Dump of assembler code for

[Bug sanitizer/78294] -fsanitize=thread broken

2016-11-11 Thread trippels at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78294 --- Comment #3 from Markus Trippelsdorf --- (gdb) up #2 0x76f8b00a in __tsan::ScopedIgnoreInterceptors::ScopedIgnoreInterceptors (this=) at ../../../../gcc/libsanitizer/tsan/tsan_rtl.h:549 549

[Bug sanitizer/78294] -fsanitize=thread broken

2016-11-10 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78294 Maxim Ostapenko changed: What|Removed |Added CC||m.ostapenko at samsung dot com ---

[Bug sanitizer/78294] -fsanitize=thread broken

2016-11-10 Thread dvyukov at google dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78294 Dmitry Vyukov changed: What|Removed |Added CC||dvyukov at google dot com --- Comment