public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/105300] segfault from static_assert with user-defined string suffix argument Date: Tue, 19 Apr 2022 14:11:24 +0000 [thread overview] Message-ID: <bug-105300-4-QVACTDBpKm@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105300-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105300 Martin Liška <marxin at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 CC| |marxin at gcc dot gnu.org Last reconfirmed| |2022-04-19 Status|UNCONFIRMED |WAITING --- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> --- Is it really a valid code since clang rejects it? $ clang++ pr105300.C -c pr105300.C:2:27: error: string literal with user-defined suffix cannot be used here static_assert(false, "foo"_x); ^ 1 error generated.
next prev parent reply other threads:[~2022-04-19 14:11 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-18 3:51 [Bug c++/105300] New: " Jack at Applin dot US 2022-04-19 14:11 ` marxin at gcc dot gnu.org [this message] 2022-04-19 17:17 ` [Bug c++/105300] " marxin at gcc dot gnu.org 2022-11-03 0:21 ` [Bug c++/105300] [10/11/12/13 Regression] " pinskia at gcc dot gnu.org 2022-11-03 0:32 ` pinskia at gcc dot gnu.org 2022-11-11 20:39 ` mpolacek at gcc dot gnu.org 2022-12-20 13:39 ` rguenth at gcc dot gnu.org 2023-01-26 15:08 ` cvs-commit at gcc dot gnu.org 2023-01-26 15:21 ` [Bug c++/105300] [10/11/12 " mpolacek at gcc dot gnu.org 2023-04-10 7:24 ` jakub 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-105300-4-QVACTDBpKm@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).