Tim Ruehsen
2016-10-28 14:05:22 UTC
Hi,
during some GNU internal discussion I was asked to post my proposal / request
here.
"I use manywarnings.m4 in my projects which take ~9s here (~25% of the whole
./configure run).
One gcc invocation per (possible) warning options sums up a lot.
gcc -Q --help=warning|awk '{ if ($2 == "[disabled]") print $1 }'
gives a complete list of available warning options which we can use without
checking each single option.
This also takes automatic advantage of new gcc warnings."
I took a look at the source but feel somewhat incompetent to provide a patch
(m4 and shell is just not my competence). It seems to be a pretty low-hanging
fruit for an expert, though.
I really would enjoy a faster manywarnings.m4 !
Regards, Tim
during some GNU internal discussion I was asked to post my proposal / request
here.
"I use manywarnings.m4 in my projects which take ~9s here (~25% of the whole
./configure run).
One gcc invocation per (possible) warning options sums up a lot.
gcc -Q --help=warning|awk '{ if ($2 == "[disabled]") print $1 }'
gives a complete list of available warning options which we can use without
checking each single option.
This also takes automatic advantage of new gcc warnings."
I took a look at the source but feel somewhat incompetent to provide a patch
(m4 and shell is just not my competence). It seems to be a pretty low-hanging
fruit for an expert, though.
I really would enjoy a faster manywarnings.m4 !
Regards, Tim