From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15446 invoked by alias); 22 Aug 2008 17:38:32 -0000 Received: (qmail 14832 invoked by uid 48); 22 Aug 2008 17:37:12 -0000 Date: Fri, 22 Aug 2008 17:38:00 -0000 Message-ID: <20080822173712.14831.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug middle-end/36902] Array bound warning with dead code after optimization In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "hjl dot tools at gmail dot com" 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: 2008-08/txt/msg01697.txt.bz2 ------- Comment #20 from hjl dot tools at gmail dot com 2008-08-22 17:37 ------- (In reply to comment #19) > (In reply to comment #18) > > I think that if the compiler knows that the code is never executed then, we > > shouldn't warn. > > It does but only later on in the optimization it knows that the code is dead. > Why can't we queue those warnings which may come from dead code and suppress them if they are dead? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36902