https://bugs.kde.org/show_bug.cgi?id=462084
Sam James <s...@gentoo.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|WAITINGFORINFO |DOWNSTREAM
--- Comment #8 from Sam James <s...@gentoo.org> ---
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.
