From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 860823857BB3; Mon, 2 Oct 2023 09:41:26 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 860823857BB3 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1696239686; bh=/Awr4I/unvi+9mtLIw+3Dd4Tt7dlk1Dy9gYB13nv9nY=; h=From:To:Subject:Date:In-Reply-To:References:From; b=fdSKMoTCGqDJ7w0UKCh9/VcIQafqbkvY4y1fU7OmYbH8eJY/GGwMpEI2wmkF77qW4 0KnDtuCyJukWdzUbp5VfKjuyXAwNGA0H4hGzfRgoUBQ+RPfBP/Xa0OsyPGAwtCUOaf GE/KE++UPFtusfX1Rq/GPKOXrjfuYJjmHlxsKmFU= From: "manu at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c/111654] Introduce clang's invalid-noreturn warning Date: Mon, 02 Oct 2023 09:41:21 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c X-Bugzilla-Version: unknown X-Bugzilla-Keywords: diagnostic X-Bugzilla-Severity: normal X-Bugzilla-Who: manu at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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=3D111654 Manuel L=C3=B3pez-Ib=C3=A1=C3=B1ez changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |manu at gcc dot gnu.org --- Comment #1 from Manuel L=C3=B3pez-Ib=C3=A1=C3=B1ez --- (In reply to Julian Waters from comment #0) > Created attachment 56022 [details] > Patch to add invalid-noreturn to gcc Patches should be submitted to gcc-patches@gcc.gnu.org For more details, please read: https://gcc.gnu.org/wiki/GettingStarted#Basics:_Contributing_to_GCC_in_10_e= asy_steps Except for clang compatibility, I believe the consensus is that numerical levels are not user-friendly. I think it would be better to have: -Wnoreturn-implicit-return -Wnoreturn-explicit-return -Winvalid-noreturn enables / disables both.=