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++/105667] Internal compiler segmentation fault
Date: Thu, 19 May 2022 23:34:55 +0000	[thread overview]
Message-ID: <bug-105667-4-h48xX4Lj5C@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

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Reduced testcase without the need for tuple includes:
template<auto f>
struct h {typedef int type;};

template<int I, class... Types>
struct t{};

template<typename Ts>
struct Example {
    using Types = typename h<[] <typename T> () {}>::type;

    static void crash() {
        auto f = [&] <int i=0> () {
            using type = t<0, Types>();
        };

        f();
    }
};

int main() {
    Example<int>::crash();
    return 0;
}

  reply	other threads:[~2022-05-19 23:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-19 23:22 [Bug c++/105667] New: " akira65535 at protonmail dot com
2022-05-19 23:34 ` pinskia at gcc dot gnu.org [this message]
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
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-h48xX4Lj5C@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).