From: Junio C Hamano <gitster@pobox.com>
To: Ramsay Jones <ramsay@ramsayjones.plus.com>
Cc: Kristoffer Haugsbakk <code@khaugsbakk.name>,
GIT Mailing-list <git@vger.kernel.org>
Subject: Re: [PATCH] name-rev: fix an 'may be used uninitialized' error
Date: Mon, 04 May 2026 10:13:01 +0900 [thread overview]
Message-ID: <xmqqv7d4ou3m.fsf@gitster.g> (raw)
In-Reply-To: <e74a8fd8-0617-46a8-8bef-a454d51a99c1@ramsayjones.plus.com> (Ramsay Jones's message of "Sun, 3 May 2026 16:16:38 +0100")
Ramsay Jones <ramsay@ramsayjones.plus.com> writes:
> Today's seen branch fails to build (with DEVELOPER=1), like so:
>
> CC builtin/name-rev.o
> builtin/name-rev.c: In function ‘cmd_format_rev’:
> builtin/name-rev.c:885:28: error: ‘commit’ may be used uninitialized [-Werror=maybe-uninitialized]
> 885 | if (!commit) {
> | ^
> builtin/name-rev.c:867:40: note: ‘commit’ was declared here
> 867 | struct commit *commit;
> | ^~~~~~
> cc1: all warnings being treated as errors
> make: *** [Makefile:2932: builtin/name-rev.o] Error 1
> ...
> diff --git a/builtin/name-rev.c b/builtin/name-rev.c
> index b941e93834..5b7f7a00e5 100644
> --- a/builtin/name-rev.c
> +++ b/builtin/name-rev.c
> @@ -882,6 +882,8 @@ int cmd_format_rev(int argc,
> peeled = deref_tag(the_repository, object, scratch_buf.buf, 0);
> if (peeled && peeled->type == OBJ_COMMIT)
> commit = (struct commit *)peeled;
> + else
> + commit = NULL;
> if (!commit) {
> fprintf(stderr, "Could not get commit for %s. Skipping.\n",
> *argv);
Why not
if (peeled && peeled->type == OBJ_COMMIT) {
commit = (struct commit *)peeled;
} else {
fprintf(stderr, "... skipping ...");
continue;
}
get_format_rev(commit, &format_pp, &scratch);
or even
if (!peeled || peeled->type != OBJ_COMMIT) {
fprintf(stderr, "... skipping ...");
continue;
}
get_format_rev((struct commit *)peeled->type,
&format_pp, &scratch);
and dropping the variable "struct commit *commit" altogether?
next prev parent reply other threads:[~2026-05-04 1:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-03 15:16 [PATCH] name-rev: fix an 'may be used uninitialized' error Ramsay Jones
2026-05-03 18:52 ` Kristoffer Haugsbakk
2026-05-04 1:13 ` Junio C Hamano [this message]
2026-05-04 8:55 ` Kristoffer Haugsbakk
2026-05-04 20:26 ` Ramsay Jones
2026-05-04 21:56 ` Kristoffer Haugsbakk
2026-05-05 0:41 ` Ramsay Jones
2026-05-05 19:09 ` Kristoffer Haugsbakk
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=xmqqv7d4ou3m.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=code@khaugsbakk.name \
--cc=git@vger.kernel.org \
--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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.