From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25456 invoked by alias); 24 Feb 2010 20:15:00 -0000 Received: (qmail 25345 invoked by uid 48); 24 Feb 2010 20:14:50 -0000 Date: Wed, 24 Feb 2010 20:15:00 -0000 Message-ID: <20100224201450.25344.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug c++/19808] miss a warning about uninitialized members in constructor 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-02/txt/msg02501.txt.bz2 ------- Comment #13 from manu at gcc dot gnu dot org 2010-02-24 20:14 ------- (In reply to comment #9) > > I'd close this one as WONTFIX or mark it as dup of a "do uninitialized > variable warnings for memory". > Please no, this perhaps could still be implemented in the C++ front-end for this particular case. Maybe there is a way to keep track of which initializers have been seen already and which members are not initialized elsewhere. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19808