[valgrind] [Bug 414870] std::frexp(long double) broken under valgrind.

2019-12-28 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=414870 Julian Seward changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|---

[valgrind] [Bug 414870] std::frexp(long double) broken under valgrind.

2019-12-06 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=414870 --- Comment #3 from Tom Hughes --- 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

[valgrind] [Bug 414870] std::frexp(long double) broken under valgrind.

2019-12-06 Thread John Maddock
https://bugs.kde.org/show_bug.cgi?id=414870 --- Comment #2 from John Maddock --- I appreciate long double is unsupported - however this did actually work. The critical change appears to be GCC-9 vc GCC-8. -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 414870] std::frexp(long double) broken under valgrind.

2019-12-05 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=414870 Tom Hughes changed: What|Removed |Added CC||t...@compton.nu --- Comment #1 from Tom Hughes