From: Jeff King <peff@peff.net>
To: Ramsay Jones <ramsay@ramsayjones.plus.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
GIT Mailing-list <git@vger.kernel.org>
Subject: Re: [PATCH 2/2] read-cache: fix an -Wmaybe-uninitialized warning
Date: Tue, 20 Mar 2018 00:36:52 -0400 [thread overview]
Message-ID: <20180320043652.GC13302@sigill.intra.peff.net> (raw)
In-Reply-To: <6d434e76-cfa0-2a6e-f163-b54316a24cee@ramsayjones.plus.com>
On Mon, Mar 19, 2018 at 05:56:11PM +0000, Ramsay Jones wrote:
> For the purposes of this discussion, the ce_write_entry() function has
> three code blocks of interest, that look like so:
>
> /* block #1 */
> if (ce->ce_flags & CE_STRIP_NAME) {
> saved_namelen = ce_namelen(ce);
> ce->ce_namelen = 0;
> }
>
> /* block #2 */
> /*
> * several code blocks that contain, among others, calls
> * to copy_cache_entry_to_ondisk(ondisk, ce);
> */
>
> /* block #3 */
> if (ce->ce_flags & CE_STRIP_NAME) {
> ce->ce_namelen = saved_namelen;
> ce->ce_flags &= ~CE_STRIP_NAME;
> }
>
> The warning implies that gcc thinks it is possible that the first
> block is not entered, the calls to copy_cache_entry_to_ondisk()
> could toggle the CE_STRIP_NAME flag on, thereby entering block #3
> with saved_namelen unset. However, the copy_cache_entry_to_ondisk()
> function does not write to ce->ce_flags (it only reads). gcc could
> easily determine this, since that function is local to this file,
> but it obviously doesn't.
Weird. It seems like it would be pretty easy for it to know that we
don't write the flags field at all. But I also don't see any other thing
that would fool the compiler.
> In order to suppress this warning, we make it clear to the reader
> (human and compiler), that block #3 will only be entered when the
> first block has been entered, by introducing a new 'stripped_name'
> boolean variable. We also take the opportunity to change the type
> of 'saved_namelen' to 'unsigned int' to match ce->ce_namelen.
These probably both ought to be size_t, but it makes sense to match
ce_namelen for now.
> diff --git a/read-cache.c b/read-cache.c
> index 2eb81a66b..49607ddcd 100644
> --- a/read-cache.c
> +++ b/read-cache.c
> @@ -2104,13 +2104,15 @@ static int ce_write_entry(git_SHA_CTX *c, int fd, struct cache_entry *ce,
> struct strbuf *previous_name, struct ondisk_cache_entry *ondisk)
> {
> int size;
> - int saved_namelen = saved_namelen; /* compiler workaround */
> int result;
> + unsigned int saved_namelen;
> + int stripped_name = 0;
Maybe too clever, but I think you could just do:
unsigned int saved_namelen = 0;
...
saved_namelen = ce_namelen(ce);
...
if (saved_namelen)
ce->ce_namelen = saved_namelen;
ce->ce_flags &= ~CE_STRIP_NAME;
the zero-length name case (if that's even legal) would work out the
same.
That probably falls under the category of bikeshedding, though.
-Peff
next prev parent reply other threads:[~2018-03-20 4:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-19 17:56 [PATCH 2/2] read-cache: fix an -Wmaybe-uninitialized warning Ramsay Jones
2018-03-20 4:36 ` Jeff King [this message]
2018-03-20 22:52 ` Ramsay Jones
2018-03-21 5:59 ` Jeff King
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180320043652.GC13302@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=ramsay@ramsayjones.plus.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).