From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4900 invoked by alias); 10 Nov 2014 12:48:49 -0000 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 Received: (qmail 4855 invoked by uid 48); 10 Nov 2014 12:48:45 -0000 From: "uweigand at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/63748] [4.9/5 Regression] wrong may be used uninitialized warning (abnormal edges) Date: Mon, 10 Nov 2014 12:48:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 5.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: uweigand at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 4.9.3 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2014-11/txt/msg00697.txt.bz2 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63748 --- Comment #6 from Ulrich Weigand --- I guess I can see why there might be an abnormal edge starting at bb 3, or at least, that the compiler might not be easily able to deduce that it isn't necessary. However, I do not understand why any of the abnormal edges *target* bb5 *before* the setjmp call. Shouldn't an abnormal edge due to a longjmp end up *after* the setjmp? After all, the setjmp itself (including the preparation of its arguments) is *not* executed twice; the effect of the longjmp is simply to make the setjmp *return* twice.