From: Patrick Steinhardt <ps@pks.im>
To: Junio C Hamano <gitster@pobox.com>
Cc: Fernando Gouveia Lima <fernandolimabusiness@gmail.com>,
git@vger.kernel.org, Christian Couder <chriscool@tuxfamily.org>,
stolee@gmail.com, peff@peff.net
Subject: Re: [Newcomer PATCH] log-tree.c: Supress Wsign-compare-warning
Date: Fri, 23 May 2025 17:12:26 +0200 [thread overview]
Message-ID: <aDCQWr3MBX4L7sbA@pks.im> (raw)
In-Reply-To: <xmqqsekx8yef.fsf@gitster.g>
On Wed, May 21, 2025 at 02:08:40PM -0700, Junio C Hamano wrote:
> Fernando Gouveia Lima fernandolimabusiness@gmail.com writes:
> Quite honestly, -Wsign-compare is mostly garbage [*] and I wish we
> did not add it to the developer settings. A more effective way to
> squelch them is not by sprinkling the casts like this, but to remove
> it from config.mak.dev ;-)
>
> https://staticthinking.wordpress.com/2023/07/25/wsign-compare-is-garbage/
I'm still not of the opinion that it is garbage. We have tons of
locations where we mismatch integer types only because we never got a
warning from the compiler, and these have caused multiple stack
overflows in the past. The signal-to-noise ratio is high, that much is
certainly true. But if it helps us to avoid security issues in the
future I think that is acceptable.
I do agree though this not a good project for newcomers, as fixing those
bugs is quite intricate overall. So we should definitely remove this
project from the microprojects page.
And in case I'm the only one who thinks that the warning has merit I'm
also happy to be overruled and have it be removed from our developer
settings.
Patrick
next prev parent reply other threads:[~2025-05-23 15:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-21 20:24 [Newcomer PATCH] log-tree.c: Supress Wsign-compare-warning Fernando
2025-05-21 21:08 ` Junio C Hamano
2025-05-23 15:12 ` Patrick Steinhardt [this message]
2025-05-23 15:25 ` Taylor Blau
2025-05-23 16:54 ` Junio C Hamano
2025-05-30 8:13 ` Patrick Steinhardt
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aDCQWr3MBX4L7sbA@pks.im \
--to=ps@pks.im \
--cc=chriscool@tuxfamily.org \
--cc=fernandolimabusiness@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=stolee@gmail.com \
/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 NNTP newsgroup(s).