On Fri, 2020-06-05 at 10:51 +0000, devel-request(a)lists.fedoraproject.org wrote:
Send devel mailing list submissions to
Date: Fri, 05 Jun 2020 12:42:03 +0200
From: Florian Weimer <fweimer(a)redhat.com>
Subject: Re: Fedora 33 System-Wide Change proposal: CompilerPolicy
Change
To: Igor Raits <ignatenkobrain(a)fedoraproject.org>
Cc: Development discussions related to Fedora
<devel(a)lists.fedoraproject.org>
Message-ID: <87pnadu744.fsf(a)oldenburg2.str.redhat.com>
Content-Type: text/plain
* Igor Raits:
> From what I see, GCC supports it on x86, x86_64, s390x, riscv64,
> ppc64le. So this just does not include ARM / AArch64 from Fedora
> architectures.
GCC has aarch64 support for stack-clash-protection, but it only works
well with 64K pages (otherwise detection is not reliable). This is due
to a choice by the target maintainers I do not understand. At least it
does not break anything.
Correct.
I don't know the state on armhfp. It used the generic GCC
implementation in the past, which we considered too buggy to enable.
I don't
think anyone ever stepped up to implement stack-clash protection on 32bit
ARM. I couldn't justify spending the time on it when stack-clash hit because
32bit ARM isn't supported by RHEL. And after doing x86, ppc, s390 and aarch64
for GCC I was burnt out as hell.
I expect LLVM 11 should have stack-clash protection for x86, ppc and s390. I'm
working with ARM to find resources to do an AArch64 implementation with the goal
of landing it for LLVM 12.
jeff