https://bugs.kde.org/show_bug.cgi?id=472329
--- Comment #7 from Paul Floyd <pjfl...@wanadoo.fr> --- After discussion on the gcc mailing list, because f is on the stack the compiler can see that dereferencing the stack memory is safe and so it allows reordering. Valgrind assumes that all memory dereferences are potentially trapping and so does not try to perform the idiom recovery. So for the moment I'm stumped. -- You are receiving this mail because: You are watching all bug changes.
