|
From: | Pádraig Brady |
Subject: | Re: coreutils and GCC -fanalyzer |
Date: | Fri, 10 Jul 2020 22:21:54 +0100 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.0 |
On 02/07/2020 01:26, Paul Eggert wrote:
On 5/23/20 9:08 AM, Paul Eggert wrote: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.I did that in Gnulib by installing the attached patch. This could greatly increase compile times due to the -fanalyzer option, so let's keep an eye out for that.
s/could/does/. compile time has gone from seconds to minutes for coreutils at least. I'd be inclined to not enable -fanalyzer by default. At least not until it matures more. -fanalyzer didn't find any actual issues in coreutils, and currently bails on most files (after taking lots of time about it), as indicated with the -Wanalyzer-too-complex option. cheers, Pádraig
[Prev in Thread] | Current Thread | [Next in Thread] |