From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28031 invoked by alias); 4 Jun 2010 15:56:53 -0000 Received: (qmail 27900 invoked by uid 48); 4 Jun 2010 15:56:30 -0000 Date: Fri, 04 Jun 2010 15:56:00 -0000 Message-ID: <20100604155630.27899.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug middle-end/44307] warning: may be used uninitialized in this function often building gcc In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "manu at gcc dot gnu dot org" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2010-06/txt/msg00493.txt.bz2 ------- Comment #4 from manu at gcc dot gnu dot org 2010-06-04 15:56 ------- Hi Jay, -Wuninitialized is quite unreliable in old compilers and also we do not know what patches Apple applies to its copy of GCC. This is why -Werror is not used in the first stage of building GCC. We do not see these warnings with recent GCC, so I guess they are bogus. If you find a real (potential) uninitialized use, please reopen this PR and point us to the code. Otherwise, fixing this is not worth the effort of anyone. There is a lot more interesting (and urgently needed) work to do in GCC. I am sure Richard Guenther could have fixed a couple of real bugs in the time it took him to read this PR ;). Thanks for the report anyway. -- manu at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |manu at gcc dot gnu dot org Status|UNCONFIRMED |RESOLVED Resolution| |WONTFIX http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44307