From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1531 invoked by alias); 27 Aug 2003 21:57:06 -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 1523 invoked by uid 48); 27 Aug 2003 21:57:05 -0000 Date: Wed, 27 Aug 2003 21:57:00 -0000 Message-ID: <20030827215705.1522.qmail@sources.redhat.com> From: "bangerth at dealii dot org" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20030827203936.12082.augart@us.ibm.com> References: <20030827203936.12082.augart@us.ibm.com> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug optimization/12082] Inappropriate unreachable code warnings X-Bugzilla-Reason: CC X-SW-Source: 2003-08/txt/msg03096.txt.bz2 List-Id: PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12082 ------- Additional Comments From bangerth at dealii dot org 2003-08-27 21:57 ------- I can confirm this, the warnings are clearly bogus. Slightly changing the code makes the locations of the problem go away or move randomly. It takes someone with some more time than me right now to reduce this, though. One of the things that startle me is that it reports warnings in functions with the wrong name (i.e. it says the problem is in function "main", but the given line number is in another function). Maybe this has something to do with inlining then. W.