From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7171 invoked by alias); 27 Apr 2007 15:45:28 -0000 Received: (qmail 7143 invoked by uid 48); 27 Apr 2007 15:45:18 -0000 Date: Fri, 27 Apr 2007 15:45:00 -0000 Message-ID: <20070427154518.7142.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug c++/18016] Warn about member variables initialized with itself In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "irving at cs dot stanford dot edu" 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: 2007-04/txt/msg02122.txt.bz2 ------- Comment #5 from irving at cs dot stanford dot edu 2007-04-27 16:45 ------- Is there any chance of activity on this bug? It would be wonderful to have a warning for this case, since these bugs can be extremely annoying to find. If the infrastructure supports it, the ideal way to resolve this might be to manually mark all fields of this uninitialized on entry to each constructor. If that's impossible because the dataflow is run only on top level variables, just checking for occurences of :a(a) would help a lot. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18016