https://bugs.kde.org/show_bug.cgi?id=404842
Tom Hughes <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REPORTED |RESOLVED CC| |[email protected] Resolution|--- |NOT A BUG --- Comment #1 from Tom Hughes <[email protected]> --- That code is just totally non thread safe, so all bets as to it's behaviour are null and void. You have two threads each of which is reading one global and writing another but there are no locks, memory barriers or other synchronisation primitives so there is no way to know when, or if, either thread will see changes made by the other. So it's completely valid for each thread to be incrementing a register and never flushing it to memory so that the other thread never sees any change. That of course is just one way it could go wrong. Just compile it with -fsanitize=thread and see how many warnings you get... -- You are receiving this mail because: You are watching all bug changes.
