GNU bug report logs - #78659
[PATCH] Pacify Clang's -Wformat-signedness.

Previous Next

Full log

Message #14 received at 78659 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Paul Eggert <eggert <at> cs.ucla.edu>
Cc: 78659 <at> debbugs.gnu.org, collin.funk1 <at> gmail.com
Subject: Re: bug#78659: [PATCH] Pacify Clang's -Wformat-signedness.
Date: Sun, 01 Jun 2025 10:29:33 +0300

> Date: Sat, 31 May 2025 23:47:15 -0700
> Cc: 78659 <at> debbugs.gnu.org
> From: Paul Eggert <eggert <at> cs.ucla.edu>
> 
> On 2025-05-31 23:24, Eli Zaretskii wrote:
> > Paul, any comments or suggestions?
> 
> As a general rule of thumb, I wouldn't bother pacifying anything but the 
> latest GCC, especially to work around false alarms (which these are). 
> Since this is isn't the latest GCC and these are false alarms, I suggest 
> ignoring the false alarms, or silencing them by using ./configure 
> --disable-gcc-warnings.

Agreed.

> Come to think of it, when building from Git maybe 'configure' should 
> make --enable-gcc-warnings the default only when using recent GCC. 

I tend to agree, but isn't the latest GCC prone to bugs in this area?

And how can we know what is "recent GCC"?

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.