public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "getchar_gnu at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/90782] internal compiler error: in dependent_type_p, at cp/pt.c:25409 Date: Tue, 15 Dec 2020 12:01:16 +0000 [thread overview] Message-ID: <bug-90782-4-UAzFiax3pY@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-90782-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90782 --- Comment #6 from getchar_gnu at hotmail dot com --- https://gcc.godbolt.org/z/qzG9jj template<class... A> struct bar { template<class B> bar(B& obj, void(B::*f)(A...)const=&B::operator()){} }; int main() { const auto f1 = [](){}; bar f8(f1); } This compiles on clang and ice on gcc
next prev parent reply other threads:[~2020-12-15 12:01 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-90782-4@http.gcc.gnu.org/bugzilla/> 2020-07-08 23:39 ` bruck.michael at gmail dot com 2020-07-08 23:40 ` bruck.michael at gmail dot com 2020-12-15 12:01 ` getchar_gnu at hotmail dot com [this message] 2021-11-28 23:13 ` pinskia at gcc dot gnu.org 2021-12-08 17:20 ` marxin at gcc dot gnu.org 2022-01-04 3:00 ` cvs-commit at gcc dot gnu.org 2022-01-04 3:00 ` pinskia 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-90782-4-UAzFiax3pY@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).