From: "Tim Rühsen" <tim.ruehsen@gmx.de>
To: "Paul Eggert" <eggert@cs.ucla.edu>, "Pádraig Brady" <P@draigBrady.com>
Cc: Gnulib bugs <bug-gnulib@gnu.org>, coreutils@gnu.org
Subject: Re: coreutils and GCC -fanalyzer
Date: Sat, 23 May 2020 18:22:37 +0200 [thread overview]
Message-ID: <04b34915-a67e-87d5-b94c-fa30dbc263a9@gmx.de> (raw)
In-Reply-To: <0f92f576-bf1c-e889-3e4a-a128455b5684@cs.ucla.edu>
[-- Attachment #1.1: Type: text/plain, Size: 1675 bytes --]
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
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-05-23 16:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <edfafbde-9e71-f8a9-600d-23cdfaee52a5@cs.ucla.edu>
[not found] ` <77400f8a-59ca-6d02-e5b1-e01ba0619237@draigBrady.com>
[not found] ` <a554e905-fa73-6618-90d7-ae3cb136e19d@cs.ucla.edu>
[not found] ` <e551aac0-e2fe-920a-d0ea-ca80695283d0@draigBrady.com>
[not found] ` <4aa67590-a0c3-603d-d2b1-f0751a28df29@cs.ucla.edu>
[not found] ` <3a074086-47f7-638f-50a8-cd7ceb46a11a@draigBrady.com>
2020-05-23 16:08 ` coreutils and GCC -fanalyzer Paul Eggert
2020-05-23 16:22 ` Tim Rühsen [this message]
2020-07-02 0:26 ` Paul Eggert
2020-07-10 21:21 ` Pádraig Brady
2020-07-10 21:37 ` Jeffrey Walton
2020-07-11 0:58 ` Paul Eggert
2020-07-11 14:26 ` Pádraig Brady
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=04b34915-a67e-87d5-b94c-fa30dbc263a9@gmx.de \
--to=tim.ruehsen@gmx.de \
--cc=P@draigBrady.com \
--cc=bug-gnulib@gnu.org \
--cc=coreutils@gnu.org \
--cc=eggert@cs.ucla.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).