Really enable -fstack-clash-protection on armhf/armel?
Hi,
it looks like enabling this flag on armel/armhf is a little bit premature.
Apparently it's not completely supported upstream, and might cause
regressions, according to
https://bugzilla.redhat.com/show_bug.cgi?id=1522678
Is that a feature that the Debian ARM32 porters and the security team
really want to support actively, despite the missing upstream support?
In Ubuntu, people tracked down segfaults due to this change in at least
valgrind and gnutls, maybe more.
Thanks, Matthias
Reply to: