https://bugs.kde.org/show_bug.cgi?id=460572
--- Comment #23 from Andrew Udvare <audv...@gmail.com> --- This bug is actually caused by using --march=native to GCC. Maybe it's specific to my CPU or how my GCC is built. Regardless, it would seem the code path in question is sensitive to CPU optimisations. I can compile a local Git clone with -march=native and get the same behaviour. When -march=native is gone, the problem is gone. Can the section of code dealing with this be marked to avoid optimisation? -- You are receiving this mail because: You are watching all bug changes.