From: Ramsay Jones <email@example.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Junio C Hamano <firstname.lastname@example.org>, Jeff King <email@example.com>,
GIT Mailing-list <firstname.lastname@example.org>
Subject: Re: [PATCH 0/2] -Wuninitialized
Date: Tue, 20 Mar 2018 23:02:29 +0000 [thread overview]
Message-ID: <email@example.com> (raw)
On 20/03/18 14:46, Johannes Schindelin wrote:
> Hi Ramsay,
> On Mon, 19 Mar 2018, Ramsay Jones wrote:
>> This series removes all 'self-initialised' variables (ie. <type> var =
>> var;). This construct has been used to silence gcc
>> '-W[maybe-]uninitialized' warnings in the past . Unfortunately, this
>> construct causes warnings to be issued by MSVC , along with clang
>> static analysis complaining about an 'Assigned value is garbage or
>> undefined'. The number of these constructs has dropped over the years
>> (eg. see  and ), so there are currently only 6 remaining in the
>> current codebase. As demonstrated below, 5 of these no longer cause gcc
>> to issue warnings.
> Thank you so much for working on this!
These patches are based on a very old branch (that goes back
at least as far as 2010, see ). (I have too many in my repo,
so it will be good to remove this one)!
> In Git for Windows, to work around the MSVC issues you mention, I have
> this ugly work-around (essentially, it has a FAKE_INIT() macro that either
> performs that GCC workaround or initializes the variable to NULL/0):
Oh, wow! (Hmm, actually that doesn't look too bad :-D )
> FWIW I just tested your patches with Visual Studio 2017 and there are no
> C4700 warnings (the equivalent of GCC's "may be uninitialized" warning)
> You can find the patches (your patches rebased onto Git for Windows'
> master, plus a patch adding the project files for Visual Studio) here:
Thanks for testing the patches.
> So here is my ACK, in case you want it ;-)
prev parent reply other threads:[~2018-03-20 23:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-19 17:53 [PATCH 0/2] -Wuninitialized Ramsay Jones
2018-03-20 4:32 ` Jeff King
2018-03-20 22:41 ` Ramsay Jones
2018-03-20 14:46 ` Johannes Schindelin
2018-03-20 23:02 ` Ramsay Jones [this message]
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:
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 \
* 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
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).