On 04/04/2018 12:45 AM, Tim Rühsen wrote:
reducing false positives > would be of great help to reduce time spent into securing code that
> uses gnulib.
Yes, and Gnulib tries to strike a balance here. For Gnulib headers, we
try harder to pacify compilers even if we think their warnings are
misguided. This particular bug report was about a .c file, though, and
for that it's reasonable to suggest that you not use the compile-time
option that enables this flag when compiling Gnulib code, as it is more
trouble than it's worth in Gnulib code.
