On 23.05.20 18:08, Paul Eggert wrote: > On 5/23/20 8:56 AM, Pádraig Brady wrote: >> Note -Wanalyzer... flags are ineffective without -fanalyzer. >> Also -Wanalyzer-too-complex (now auto enabled by gnulib) is currently quite >> problematic with -fanalyzer. > > Hmm, that's odd, since I recall getting more warnings with those flags > enabled. > Perhaps not all of them are disabled when you don't use -fanalyzer? Or maybe > my > memory is faulty. > > Anyway, cleary the Gnulib manywarnings module needs to be fixed to do a better > job here, and this reminds me of another problem that has been bothering me > for > quite some time: ./configure spends way too much time testing for individual > warnings when the manywarnings module is in use. So I am thinking of killing > two > stones by doing the following. > > 1. Test for -fanalyzer, -Wall, -Wextra. > > 2. Test for flags not automatically enabled by -fanalyzer, -Wall, -Wextra but > flags that we want anyway. > > 3. Test for flags automatically enabled by -fanalyzer, -Wall, -Wextra that are > also flags that we don't want. > > This should make 'configure' much faster. It'll also fix the issue you > mentioned. And we can make sure that -Wanalyzer-too-complex is not mentioned > in > step (2) so that Gnulib won't generate it.
This has been done for Wget2 https://gitlab.com/gnuwget/wget2/-/blob/master/m4/wget_manywarnings.m4 Example usage at L123+: https://gitlab.com/gnuwget/wget2/-/blob/master/configure.ac To make it usable for other projects, it needs some merging with the manywarnings.m4 from gnulib, IMO. I would support any volunteer as good as i can. Regards, Tim
signature.asc
Description: OpenPGP digital signature
