https://bugs.kde.org/show_bug.cgi?id=414870
--- Comment #3 from Tom Hughes <[email protected]> --- Well sure gcc may have generated different code. The point is that once you use long double on x86-32 there is no guarantee you will get the same results under valgrind as when running natively. You might, but you might not. Actually that can be true even with double because gcc by default generates code that can keep values on the x87 stack between operations, so 80 bit precision is used until gcc needs to move the value back to memory. Using -ffloat-store can reduce that by forcing it to move stuff back to memory more often, or just use -mfpmath=sse to make it use SSE for floating point where you will get standard IEEE semantics. -- You are receiving this mail because: You are watching all bug changes.
