From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16491 invoked by alias); 22 May 2008 10:21:50 -0000 Received: (qmail 16414 invoked by uid 48); 22 May 2008 10:21:07 -0000 Date: Thu, 22 May 2008 10:21:00 -0000 Message-ID: <20080522102107.16413.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug middle-end/36296] wrong warning about potential uninitialized variable In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "rguenth 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: 2008-05/txt/msg01691.txt.bz2 ------- Comment #3 from rguenth at gcc dot gnu dot org 2008-05-22 10:21 ------- A way to tell gcc a variable is not uninitialized is to perform self-initialization like int i = i; this will cause no code generation but inhibits the warning. Other compilers may warn about this construct of course. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36296