From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31487 invoked by alias); 25 Apr 2007 22:59:35 -0000 Received: (qmail 31470 invoked by uid 48); 25 Apr 2007 22:59:25 -0000 Date: Wed, 25 Apr 2007 22:59:00 -0000 Message-ID: <20070425225925.31469.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug middle-end/31707] Spurious "'' may be used uninitialized in this function" warnings when using __builtin_setjmp and loops and extern function call In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "pinskia 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: 2007-04/txt/msg01960.txt.bz2 ------- Comment #5 from pinskia at gcc dot gnu dot org 2007-04-25 23:59 ------- The problem is that the CFG does not know that the first time through the loop when calling bar, you cannot get to the setjmp. This is a hard problem to solve really. You have to track the uninitialized variable usage your solve to solve it correctly. -- pinskia at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- GCC host triplet|mingw32 | GCC target triplet|mingw32 | Keywords| |diagnostic Summary|Spurious "'' may |Spurious "'' may |be used uninitialized in |be used uninitialized in |this function" warnings when|this function" warnings when |using __builtin_setjmp |using __builtin_setjmp and | |loops and extern function | |call http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31707