From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11935 invoked by alias); 12 May 2012 12:31:59 -0000 Received: (qmail 11923 invoked by uid 22791); 12 May 2012 12:31:58 -0000 X-SWARE-Spam-Status: No, hits=-4.3 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00,KHOP_THREADED X-Spam-Check-By: sourceware.org Received: from localhost (HELO gcc.gnu.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sat, 12 May 2012 12:31:45 +0000 From: "manu at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/50847] missed warning about unreachable code after throw statment. Date: Sat, 12 May 2012 12:36: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-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: manu at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: CC Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 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: 2012-05/txt/msg01306.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D50847 Manuel L=C3=B3pez-Ib=C3=A1=C3=B1ez changed: What |Removed |Added ---------------------------------------------------------------------------- CC|lopezibanez at gmail dot |manu at gcc dot gnu.org |com | --- Comment #4 from Manuel L=C3=B3pez-Ib=C3=A1=C3=B1ez 2012-05-12 12:31:14 UTC --- (In reply to comment #1) > Manuel, could you improve gcc diagnostics in this area? Sorry but the little free time I have for GCC is going to be focused on improving the options machinery and the caret diagnostics. I may try to push for colors, if I find the time. Unfortunately, we are very very few working on C/C++ FEs right now. In this case, I am not even sure how this could be implemented in the FE without some kind of control-flow graph.