From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16872 invoked by alias); 25 Apr 2011 21:38:31 -0000 Received: (qmail 16843 invoked by uid 22791); 25 Apr 2011 21:38:30 -0000 X-SWARE-Spam-Status: No, hits=-6.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 25 Apr 2011 21:38:11 +0000 Received: from int-mx02.intmail.prod.int.phx2.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id p3PLc8wp006839 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 25 Apr 2011 17:38:08 -0400 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx02.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id p3PLc8Mw010251; Mon, 25 Apr 2011 17:38:08 -0400 Received: from [10.3.113.96] (ovpn-113-96.phx2.redhat.com [10.3.113.96]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id p3PLc7Ld010667; Mon, 25 Apr 2011 17:38:07 -0400 Message-ID: <4DB5E9BE.7090205@redhat.com> Date: Mon, 25 Apr 2011 22:24:00 -0000 From: Jeff Law User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.15) Gecko/20110307 Fedora/3.1.9-0.39.b3pre.fc14 Lightning/1.0b3pre Thunderbird/3.1.9 MIME-Version: 1.0 To: Xinliang David Li CC: GCC Patches Subject: Re: new option -Wno-maybe-uninitialized References: <4DB0679C.9050100@redhat.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org X-SW-Source: 2011-04/txt/msg02004.txt.bz2 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 04/21/11 11:43, Xinliang David Li wrote: > > There are three different kind of uninit warnings: > > 1) definitely uninitialized, and the use the variable dominates the > exit -- this is the must be used uninitialized case > 2) definitely uninitialized, but the use may not be executed at runtime; > 3) Only initialized in some paths from entry to the use (the use may > or may not be executed). > > Currently 2) and 3) uses the same warning message, which may be misleading. > > The proposed new option only controls 3). It's certainly possible to have an uninitialized use dominating an exit which can never be executed (think infinite loop which can't be detected at compile time. I bring these issues up primarily to get us thinking about how better to describe the scenarios where we warn in our documentation. I don't want to hold up real improvements. > >> No, the patch does not change the default behavior of -Wuninitialized >> wihch will turn on -Wmaybe-uninitialized as well. The only useful >> scenarios for the new option are: OK. I must have misread something. Given the fact that your patch isn't changing the -Wuninitialized behaviour, then let's go ahead with your patch. Jeff -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJNtem+AAoJEBRtltQi2kC7f54IALq8+i2dtRw2z/r6rKYX6+JD u0eraT4+U5q58ZQQZeU05eBKv4P3Soq14z4/RuuM7dTuU44fqOKz4IrvAxUmnm9f pdQy4OWHs1/vMR/04JdYy2IjDNbx9tRADioD4VvgrvfBSYHhZvLTJHg5ggAmk2eS S1Dd1tnKrfn/h0Bz3wqwNDblAQT2TzUvYRcBEq+iTzBQWbrkCCKLr+rWIxEeCDGn 679hkhiFeUYcoFSvYIXc54YCYWCjWsdj5n3Fg9ex7IWGblvfjPejUfq//Xr2wq0J jlDfuo3mDoDEgLxQ94RRMeHYf7kwCRhwiYqul/U2Fg7UOHlci2aWKpCfHEdY5VI= =no9V -----END PGP SIGNATURE-----