public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.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 [thread overview] Message-ID: <bug-113366-4-mpWlrCg37F@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113366-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113366 --- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> --- It seems like there's no macro predefined by the front end to tell me -fconcepts-ts is being used? It defines __cpp_concepts=201507L for C++17 mode, but for C++20 that is __cpp_concepts=202002L instead (as required for C++20). If there was a macro telling me the non-C++20 -fconcepts-ts parsing code was 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.
next prev parent reply other threads:[~2024-01-13 11:48 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-13 0:33 [Bug testsuite/113366] New: " mpolacek at gcc dot gnu.org 2024-01-13 11:32 ` [Bug testsuite/113366] " redi at gcc dot gnu.org 2024-01-13 11:40 ` redi at gcc dot gnu.org 2024-01-13 11:48 ` redi at gcc dot gnu.org [this message] 2024-01-15 17:18 ` cvs-commit at gcc dot gnu.org 2024-01-18 21:03 ` cvs-commit at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-113366-4-mpWlrCg37F@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).