On Sun, Feb 11, 2018 at 6:56 PM, Kees Cook <keesc...@chromium.org> wrote: > Old? That's not the case. The check for -fno-stack-protector will > likely be needed forever, as some distro compilers enable > stack-protector by default. So when someone wants to explicitly build > without stack-protector (or if the compiler's stack-protector is > detected as broken), we must force it off for the kernel build.
What I meant is whether it makes sense to test if the -fno-stack-protector option is supported. Can we reasonably assume that passing -fno-stack-protector to the compiler won't cause an error? Is it possible to build GCC with no "no stack protector" support? Do we need to support any compilers that would choke on the -fno-stack-protector flag itself? If we can reasonably assume that passing -fno-stack-protector is safe, then CC_HAS_STACKPROTECTOR_NONE isn't needed. Cheers, Ulf