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 libstdc++/100676] Redeclaring __failed_assertion() at every point of use of __glibcxx_assert breaks Clang CUDA Date: Thu, 20 May 2021 10:10:34 +0000 [thread overview] Message-ID: <bug-100676-4-XGpfS0XyiA@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100676-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100676 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |11.2 --- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> --- Using __builtin_unreachable works, and the diagnostic seems acceptable: In file included from /home/jwakely/gcc/12/include/c++/12.0.0/iosfwd:38, from /home/jwakely/gcc/12/include/c++/12.0.0/string_view:40, from sv.C:1: sv.C:5:21: in 'constexpr' expansion of 'f()' sv.C:3:56: in 'constexpr' expansion of 's.std::basic_string_view<char>::front()' /home/jwakely/gcc/12/include/c++/12.0.0/string_view:251:9: error: '__builtin_unreachable()' is not a constant expression 251 | __glibcxx_assert(this->_M_len > 0); | ^~~~~~~~~~~~~~~~
next prev parent reply other threads:[~2021-05-20 10:10 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-19 11:13 [Bug libstdc++/100676] New: " joachim at joameyer dot de 2021-05-19 11:57 ` [Bug libstdc++/100676] " redi at gcc dot gnu.org 2021-05-20 10:10 ` redi at gcc dot gnu.org [this message] 2021-05-20 20:49 ` cvs-commit at gcc dot gnu.org 2021-06-02 13:43 ` cvs-commit at gcc dot gnu.org 2021-06-02 13:45 ` redi 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-100676-4-XGpfS0XyiA@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).