On Sat, Feb 10, 2018 at 8:46 PM, Linus Torvalds
<torvalds@xxxxxxxxxxxxxxxxxxxx> wrote:
>
> Argh. I wanted to get rid of all that entirely, and simplify this all.
> The mentioned script (and bugzilla) was from 2006, I assumed this was
> all historical.
>
> But if it has broken again since, I guess we need to have a silly script. Grr.
Ok, so this really ended up bothering me.
I was hoping to really just unify all the stupid compiler flag testing
in just the Kconfig files and hoping we could really just use
config CC_xyz
bool
option cc_option "-fwhatever-xyz"
to set them, and then build Kconfig rules from that:
config USE_xyz
bool "Some question that needs xyz"
depends on CC_xyz
and have a nice simple
ccflags-$(CONFIG_USE_xyz) += -fwhataver-xyz
in the Makefiles.
And one thought I had was "hey, if we need a script for
-fstack-protector, maybe we can simply standardize on _everything_
using a script".
But doing the stats, we test about two _hundred_ different compiler
options, and it really looks like -fstack-protector is the _only_ one
that uses a dedicated script. Everything else is just using the "see
if the compiler accepts the flag". So no, we wouldn't want to
standardize around a script.
We do have a script for some other build options related to gcc
breakage, but not command line flags per se: both 'asm goto' and for
gcc version generation. And gcc plugin compatibility checking.
Oh well. It looks like we really have to have those nasty exceptions
from the normal rules.
Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-s390" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
