From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24506 invoked by alias); 21 Mar 2003 01:35:59 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 24477 invoked by uid 48); 21 Mar 2003 01:35:59 -0000 Date: Fri, 21 Mar 2003 01:35:00 -0000 Message-ID: <20030321013559.24476.qmail@sources.redhat.com> To: bobsummerwill@ea.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org From: bangerth@dealii.org Reply-To: bangerth@dealii.org, bobsummerwill@ea.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: c/10175: [3.3/3.4 regression] -Wunreachable-code broken X-SW-Source: 2003-03/txt/msg01361.txt.bz2 List-Id: Old Synopsis: -Wunreachable-code appears broken for one-line blocks. New Synopsis: [3.3/3.4 regression] -Wunreachable-code broken State-Changed-From-To: open->analyzed State-Changed-By: bangerth State-Changed-When: Fri Mar 21 01:35:59 2003 State-Changed-Why: Confirmed, the warning is only displayed for the multi-statement block. However, what is worse: for 3.3 and present mainline, the warning isn't generated _at all_, so this is a regression. All this is the same for the C and C++ front ends, by the way, so I put it into the more generic "C" category. W. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10175