https://bugs.kde.org/show_bug.cgi?id=339330
--- Comment #4 from Paul Floyd <[email protected]> --- I don't think that the 2nd hazard that I saw was related. It should be suppressed by { helgrind-glibc2X-004 Helgrind:Race obj:@GLIBC_LIBC_PATH@ } (Note that this is a super broad suppression which suppresses every leaf function in glibc. Probably most are thread safe but POSIX doesn't require all to be https://pubs.opengroup.org/onlinepubs/9699919799/functions/V2_chap02.html#tag_15_09_01) I guess that I was seeing that hazard before the suppression file got made glibc path agnostic. As far as I know printf is thread safe. I just tried the original example again (RHEL 7.9, GCC 11.2) and get no error. Getting back to my original idea of using a suppression. That's not so bad but it will only work with debug builds / builds with -fno-inline. In optimized builds "std::atomic<bool>::operator=(bool)" gets inlined. -- You are receiving this mail because: You are watching all bug changes.
