From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 03F213858D33; Thu, 26 Jan 2023 07:35:37 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 03F213858D33 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1674718538; bh=k8Ukcg2U4xHT53kxXT5pcDaVUivU9VLBZNtUm6tW/0M=; h=From:To:Subject:Date:In-Reply-To:References:From; b=psR6XUOtk5XCRzDxBi1uQQGcmk7E/M1ImK5Lt4Q/ZGlh5Q3n6BLvyiOk+y2+JOxPL xcwFlIUDNZuC8120JIM0qmKIDQw0+uNbKf8Fja/DA8uyIgo1LlhczQatMRayaNhHwM mxV7mf2PdWOyVNIOD+MAN6qFFyABWje5aoEUBge0= From: "rguenth at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug modula2/108551] gcc/m2/gm2-libs-pim/Termbase.mod:128:1: error: control reaches end of non-void function [-Werror=return-type] Date: Thu, 26 Jan 2023 07:35:37 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: modula2 X-Bugzilla-Version: 13.0 X-Bugzilla-Keywords: build, diagnostic X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenth at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: gaius at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: keywords Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D108551 Richard Biener changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |build, diagnostic --- Comment #1 from Richard Biener --- The function is PROCEDURE KeyPressed () : BOOLEAN ; BEGIN IF rStack=3DNIL THEN Halt(__FILE__, __LINE__, __FUNCTION__, 'no active status procedure') ELSE RETURN( rStack^.s() ) END END KeyPressed ; I'm not sure how the middle-end diagnostic issued from CFG build is confused here though, I'm not yet familiar with using cc1gm2 to debug things, nor produce standalone modula-2 testcases ;) It also means people might see bogus diagnostics for code like this.=