public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/99505] ICE Segmentation fault when decltype lambda in parameter list
Date: Sat, 13 Apr 2024 07:41:01 +0000 [thread overview]
Message-ID: <bug-99505-4-U1AuQU6Qof@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99505-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99505
--- Comment #7 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to 康桓瑋 from comment #2)
> int main() {
> [] (decltype([]{})) {} ();
> }
This testcase still ICEs.
Note clang, EDG and MSVC all reject it with a similar message here is clang's:
```
<source>:3:3: error: no matching function for call to object of type '(lambda
at <source>:3:3)'
3 | [] (decltype([]{})) {} ();
| ^~~~~~~~~~~~~~~~~~~~~~
<source>:3:3: note: candidate function not viable: requires 1 argument, but 0
were provided
3 | [] (decltype([]{})) {} ();
| ^ ~~~~~~~~~~~~~~
<source>:3:3: note: conversion candidate of type 'void (*)(decltype([] {
}))' (aka 'void (*)((lambda at <source>:3:16))')
```
prev parent reply other threads:[~2024-04-13 7:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 5:00 [Bug c++/99505] New: " hewillk at gmail dot com
2021-03-10 7:44 ` [Bug c++/99505] " marxin at gcc dot gnu.org
2021-03-10 8:18 ` hewillk at gmail dot com
2021-03-10 8:26 ` marxin at gcc dot gnu.org
2021-03-10 8:27 ` marxin at gcc dot gnu.org
2021-10-17 20:05 ` pinskia at gcc dot gnu.org
2022-01-20 3:36 ` pinskia at gcc dot gnu.org
2024-04-13 7:41 ` pinskia at gcc dot gnu.org [this message]
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-99505-4-U1AuQU6Qof@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: link
Be 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).