From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id EEA31385E838; Sat, 13 Jan 2024 11:48:49 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org EEA31385E838 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1705146529; bh=18XCBOqYKop0CGB4cL5RVtiQDZZyzM+8B7FqhcxyX1Q=; h=From:To:Subject:Date:In-Reply-To:References:From; b=RAFShG+KEyY9PT/O4Ejw2FvnBwrwdwwNDCQilgJ4dfvFVOho5cu4EVNXre0MMeisS lmQYRNIPghilpUq4MVvyFIDg6ZtD2xAq3e5+FPMrL7NSF2S4ZLXXfqLTZw0WT/Fvi7 Z/FQHnNGg9Z3Adgc/f2/PrFIGLDGLZ3LyJOINb/Q= From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/113366] g++.dg/cpp2a/concepts-pr67774.C FAIL Date: Sat, 13 Jan 2024 11:48:49 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: testsuite X-Bugzilla-Version: 14.0 X-Bugzilla-Keywords: testsuite-fail X-Bugzilla-Severity: normal X-Bugzilla-Who: redi at gcc dot gnu.org X-Bugzilla-Status: NEW 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: 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=3D113366 --- Comment #3 from Jonathan Wakely --- It seems like there's no macro predefined by the front end to tell me -fconcepts-ts is being used? It defines __cpp_concepts=3D201507L for C++17 = mode, but for C++20 that is __cpp_concepts=3D202002L instead (as required for C++= 20). If there was a macro telling me the non-C++20 -fconcepts-ts parsing code wa= s in use, I could just omit the always_inline attributes entirely. That would be simpler. Having no way to tell that the compiler is in a broken^W non-conforming mode isn't helpful.=