public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ppalka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/100557] [concepts] Internal compiler error: Error reporting routines re-entered. Date: Fri, 18 Mar 2022 16:06:09 +0000 [thread overview] Message-ID: <bug-100557-4-JqkVrqFheB@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100557-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100557 --- Comment #3 from Patrick Palka <ppalka at gcc dot gnu.org> --- Reduced: template <typename _Tp> _Tp declval(); struct print_tag_; bool tag_invoke(print_tag_, auto); bool tag_invoke(print_tag_, auto obj) requires requires { *obj; }; template <typename CPO, typename... Args> auto try_tag_invoke() noexcept(tag_invoke(declval<CPO>, declval<Args>()...)) -> decltype(tag_invoke(CPO(), declval<Args>()...)); struct print_tag_ { void operator()(auto... args) noexcept(noexcept( try_tag_invoke<print_tag_, decltype(args)...>())); } print; void foo() { print(0); }
next prev parent reply other threads:[~2022-03-18 16:06 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-12 5:22 [Bug c++/100557] New: [ICE] " ldalessandro at gmail dot com 2021-05-12 5:23 ` [Bug c++/100557] " ldalessandro at gmail dot com 2021-10-05 18:57 ` ldalessandro at gmail dot com 2021-11-03 18:04 ` [Bug c++/100557] [concepts] " ppalka at gcc dot gnu.org 2022-03-18 16:06 ` ppalka at gcc dot gnu.org [this message] 2023-05-18 1:34 ` [Bug c++/100557] [11/12/13 Regression] " pinskia at gcc dot gnu.org 2023-05-29 10:04 ` jakub at gcc dot gnu.org 2024-03-26 0:22 ` [Bug c++/100557] [11/12/13/14 " mpolacek at gcc dot gnu.org 2024-03-26 14:43 ` cvs-commit at gcc dot gnu.org 2024-03-26 14:48 ` mpolacek 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-100557-4-JqkVrqFheB@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).