Re: Really enable -fstack-clash-protection on armhf/armel?

2023-11-24 Thread Wookey
On 2023-11-24 01:34 +0100, Guillem Jover wrote: > On Thu, 2023-11-23 at 10:45:33 +0100, Matthias Klose wrote: > > it looks like enabling this flag on armel/armhf is a little bit premature. > > In Ubuntu, people tracked down segfaults due to this change in at least > > valgrind and gnutls, maybe

Re: Really enable -fstack-clash-protection on armhf/armel?

2023-11-24 Thread Adrien Nader
Hi, Short introduction: I work at Canonical in the Foundations team and made changes in gnutls which is one of the packages that first encountered/caused issues which then started blocking various migrations and changes. On Fri, Nov 24, 2023, Matthias Klose wrote: > On 24.11.23 07:19, Emanuele

Re: Really enable -fstack-clash-protection on armhf/armel?

2023-11-24 Thread Florian Weimer
* Emanuele Rocca: > Hello! > > On 2023-11-24 01:34, Guillem Jover wrote: >> According to https://bugs.debian.org/918914#73 there were no pending >> toolchain issues related to this. > > That is correct. The GCC maintainers at Arm confirm that > stack-clash-protection is supported on 32 bit too.

Re: Really enable -fstack-clash-protection on armhf/armel?

2023-11-24 Thread Matthias Klose
On 24.11.23 07:19, Emanuele Rocca wrote: Hello! On 2023-11-24 01:34, Guillem Jover wrote: According to https://bugs.debian.org/918914#73 there were no pending toolchain issues related to this. That is correct. The GCC maintainers at Arm confirm that stack-clash-protection is supported on 32