From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6385 invoked by alias); 2 Jun 2005 18:40:29 -0000 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 Received: (qmail 6359 invoked by uid 48); 2 Jun 2005 18:40:23 -0000 Date: Thu, 02 Jun 2005 18:40:00 -0000 Message-ID: <20050602184023.6358.qmail@sourceware.org> From: "trt at acm dot org" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20050416165638.21059.schwab@suse.de> References: <20050416165638.21059.schwab@suse.de> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug middle-end/21059] Bogus warning about clobbered variable X-Bugzilla-Reason: CC X-SW-Source: 2005-06/txt/msg00257.txt.bz2 List-Id: ------- Additional Comments From trt at acm dot org 2005-06-02 18:40 ------- The current warning algorithm is too simple. This would be better: For each function that contains call(s) to setjmp(), compute: ref_nz The set of variables that might possibly be live (referenced) after a setjmp() returns a non-zero value. set_any The set of variables that might possibly be set (defined) after a call to setjmp() returns. Issue a warning for all variables in the intersection of the sets. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21059