From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24870 invoked by alias); 11 Jan 2010 19:08:16 -0000 Received: (qmail 24649 invoked by uid 48); 11 Jan 2010 19:08:00 -0000 Date: Mon, 11 Jan 2010 19:08:00 -0000 Message-ID: <20100111190800.24646.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug middle-end/42674] [4.4/4.5 Regression] Bogus "no return statement in function returning non-void" warning In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "davek at gcc dot gnu dot org" 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: 2010-01/txt/msg01261.txt.bz2 ------- Comment #4 from davek at gcc dot gnu dot org 2010-01-11 19:07 ------- (In reply to comment #3) > (even without the __noreturn__?) Yes, even without. > I think this may be actually two bugs, one is the noreturn which should set > current_function_returns_abnormally to true, so no warning. Another is that the > function is not marked as never returning because of the infinite loop. Sounds right to me. Ok to leave them both under this one PR, or should we separate them? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42674