From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17207 invoked by alias); 2 Feb 2005 07:13:18 -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 16875 invoked by uid 48); 2 Feb 2005 07:12:57 -0000 Date: Wed, 02 Feb 2005 07:13:00 -0000 Message-ID: <20050202071257.16874.qmail@sourceware.org> From: "rth at gcc dot gnu dot org" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20041217160338.19058.bh@techhouse.brown.edu> References: <20041217160338.19058.bh@techhouse.brown.edu> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug tree-optimization/19058] [4.0 Regression] setjmp: 4.0 fails to give 'clobbered' warning (regression from 3.4.1) X-Bugzilla-Reason: CC X-SW-Source: 2005-02/txt/msg00177.txt.bz2 List-Id: ------- Additional Comments From rth at gcc dot gnu dot org 2005-02-02 07:12 ------- The warning has *always* been specifically dependant on which registers are assigned to which decls. So it was never assured that you'd get the warning when you actually needed it. In this case you're doubly screwed because you expect gcc to magically follow the path from "*x" through the signal handler, through to setjmp. Well, we're not going to do that. INVALID or WONTFIX, your choice. -- What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |WONTFIX http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19058