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

Previous Next

Full log

Message #28 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: Mon, 02 Jun 2025 10:52:14 +0300

> Date: Mon, 2 Jun 2025 00:26:30 -0700
> Cc: collin.funk1 <at> gmail.com, 78659 <at> debbugs.gnu.org
> From: Paul Eggert <eggert <at> cs.ucla.edu>
> 
> On 2025-06-01 00:29, Eli Zaretskii wrote:
> > I tend to agree, but isn't the latest GCC prone to bugs in this area?
> 
> Not that I know of. I usually build with it.
> 
> > And how can we know what is "recent GCC"?
> 
> I suggest worrying only about the most recent stable GCC release. 
> Anything older than that is generally not worth worrying about, though 
> there may be some exceptions in extremely annoying circumstances. After 
> all, these warnings are meant only for developers who should be using 
> recent GCC anyway.

OK, but the question of how to recognize that version still stand.
Assuming we want to enable the warning automatically by some autoconf
test, that is.

Previous Next

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