https://bugs.kde.org/show_bug.cgi?id=464140
Sam James <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |DOWNSTREAM Status|REPORTED |RESOLVED --- Comment #2 from Sam James <[email protected]> --- At this point, I suspect it's a bug in Clang's implementation of -fstack-clash-protection, given we've seen some odd behaviour with Chromium too. GCC's implementation of stack clash protection works fine. We've stopped enabling it by default for Clang. -- You are receiving this mail because: You are watching all bug changes.
