public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "nickhuang99 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/104537] New: ICE when generic-lambda as function parameter fails to be converted to pointer to function Date: Tue, 15 Feb 2022 00:53:46 +0000 [thread overview] Message-ID: <bug-104537-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104537 Bug ID: 104537 Summary: ICE when generic-lambda as function parameter fails to be converted to pointer to function Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: nickhuang99 at hotmail dot com Target Milestone: --- Consider this invalid conversion for this generic-lambda to pointer to function which is defined by "decltype(+[](T&& t )->T{return t+1;}". This ICE happens when original accepted parameter type changed from "T" to "T&&". See compiler explorer (https://www.godbolt.org/z/fde1bc3zE) I suspect this is some related issue with another unconfirmed case PR104358. template<typename T> auto foo(T&& t, decltype(+[](T&& t )->T{return t+1;}) lam){ return lam(t); } void test(){ foo<int>(5, [](int t){return t+1;}); } <source>:8:21: error: invalid user-defined conversion from 'test()::<lambda(int)>' to 'int (*)(int&&)' [-fpermissive] 8 | foo<int>(5, [](int t){return t+1;}); | ^~~~~~~~~~~~~~~~~~~~~~ ... internal compiler error: error reporting routines re-entered. 0x2174365 warning_at(unsigned int, int, char const*, ...) ...
next reply other threads:[~2022-02-15 0:53 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-15 0:53 nickhuang99 at hotmail dot com [this message] 2022-02-24 11:17 ` [Bug c++/104537] " marxin at gcc dot gnu.org 2024-04-13 8:05 ` 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-104537-4@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).