-fstack-check is _not_ a safe flag:
* 
https://developers.redhat.com/blog/2017/09/25/stack-clash-mitigation-gcc-background
* 
https://developers.redhat.com/blog/2019/04/30/stack-clash-mitigation-in-gcc-why-fstack-check-is-not-the-answer

Nobody is really interested in maintaining this functionality upstream in GCC
anymore for this reason, it's not IIRC supported in Clang, and we're not testing
it either.

Please use the far superior -fstack-clash-protection instead.

Signed-off-by: Sam James <s...@gentoo.org>
---
 eclass/flag-o-matic.eclass | 1 -
 1 file changed, 1 deletion(-)

diff --git a/eclass/flag-o-matic.eclass b/eclass/flag-o-matic.eclass
index 3dd39c54a5317..be169f934c026 100644
--- a/eclass/flag-o-matic.eclass
+++ b/eclass/flag-o-matic.eclass
@@ -51,7 +51,6 @@ _setup-allowed-flags() {
 
                # Hardening flags
                '-fstack-protector*'
-               '-fstack-check*' -fno-stack-check
                -fstack-clash-protection
                '-fcf-protection=*'
                -fbounds-check -fbounds-checking
-- 
2.40.1


Reply via email to