From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4252 invoked by alias); 27 Dec 2005 12:23:03 -0000 Received: (qmail 4223 invoked by uid 48); 27 Dec 2005 12:22:59 -0000 Date: Tue, 27 Dec 2005 12:23:00 -0000 Message-ID: <20051227122259.4222.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug c/25575] some uninitialized warning disappear when compile without -O In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "steven at gcc dot gnu dot org" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2005-12/txt/msg02637.txt.bz2 List-Id: ------- Comment #1 from steven at gcc dot gnu dot org 2005-12-27 12:22 ------- That happens because data flow information is used to find uninitialized variables. Some folks argue that this by itself is a bug, and that it should be entirely up to the front end to diagnose uninitialized variables. But then a lot of warnings could not be issued because the front ends don't have the means to compute which variables are initialized on one path through the program but not on another. In short, this is the result of a design decision. -- steven at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |WONTFIX http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25575