From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 31FB53858D33; Fri, 29 Mar 2024 01:23:03 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 31FB53858D33 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1711675383; bh=CXPYHlU62ZTmyUW5un4PoCSfmEB0whDQyE+5x4TGDCc=; h=From:To:Subject:Date:In-Reply-To:References:From; b=uMy9qbDmUl88KMQNj1bUGmeoRkuA+8J6XKGsQE2kEFVKWwORC2GaUeqvr5GGvuBt8 opJt9hzgkzQ/yvfVzJxWKEnUkxQVL/g+eXlR/pD8TOABq0Q40dm53WZiMLRC7ngbw9 HbJQ+RYNG122b6d5klk1IhPtATzhgcTHA6RDA7ps= From: "harald at gigawatt dot nl" To: gcc-bugs@gcc.gnu.org Subject: [Bug c/114526] ISO C does not prohibit extensions: fix misconception. Date: Fri, 29 Mar 2024 01:23:02 +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: 14.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: harald at gigawatt dot nl X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: DUPLICATE 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: 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=3D114526 --- Comment #6 from Harald van Dijk --- (In reply to Joseph S. Myers from comment #5) > The -pedantic documentation was updated to reflect reality - that the opt= ion > is about more than just when diagnostics are required by ISO C ("forbidden > extensions" can be taken, in the C case, as meaning those that involve > constraint violations or are outside the standard C syntax) but covers so= me > other programs doing things not defined in ISO C as well - in commit > 074e95e34275d72664f997ed949d9c91e37cd6ee (July 2000). I don't think any > possible narrower intent there may have been long before then is > particularly relevant now. Actually, the narrower intent is still documented at . Arguably, th= is behaviour makes -ansi -pedantic-errors a non-conforming implementation beca= use it rejects code that is only undefined at runtime, which ISO C requires implementations to accept unless the implementation can prove the code is reached.=