public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "blubban at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/105667] [C++20] lambas in template argument sometimes causes an ICE (seg fault)
Date: Fri, 30 Jun 2023 19:56:46 +0000 [thread overview]
Message-ID: <bug-105667-4-abmxIgzqEy@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105667-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105667
Alfred Agrell <blubban at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |blubban at gmail dot com
--- Comment #8 from Alfred Agrell <blubban at gmail dot com> ---
I ran into something similar. My reduced testcase is
struct class1
{
virtual void a_function() = 0;
};
template<auto my_lambda = []<typename T>() {}>
class class2 {};
template<typename Touter>
struct class3 : public class1 {
void a_function()
{
class2<> x;
}
};
struct class4 : public class3<class4> {
class4() {}
};
https://godbolt.org/z/GKo5oWe8j
next prev parent reply other threads:[~2023-06-30 19:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-19 23:22 [Bug c++/105667] New: Internal compiler segmentation fault akira65535 at protonmail dot com
2022-05-19 23:34 ` [Bug c++/105667] " pinskia at gcc dot gnu.org
2022-05-19 23:47 ` [Bug c++/105667] [C++20] lambas in template argument sometimes causes an ICE (seg fault) pinskia at gcc dot gnu.org
2022-05-19 23:48 ` pinskia at gcc dot gnu.org
2022-05-19 23:51 ` pinskia at gcc dot gnu.org
2022-05-20 7:50 ` marxin at gcc dot gnu.org
2022-09-04 17:40 ` pobrn at protonmail dot com
2023-05-08 21:27 ` eric.niebler at gmail dot com
2023-06-30 19:56 ` blubban at gmail dot com [this message]
2024-04-13 20:24 ` [Bug c++/105667] [C++20] lambdas in template argument sometimes cause " 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-105667-4-abmxIgzqEy@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).