public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pobrn at protonmail 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: Sun, 04 Sep 2022 17:40:12 +0000 [thread overview] Message-ID: <bug-105667-4-uuJdwhwZja@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 Barnabás Pőcze <pobrn at protonmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pobrn at protonmail dot com --- Comment #6 from Barnabás Pőcze <pobrn at protonmail dot com> --- Another snippet that I believe triggers the same issue: template<typename> struct get { }; template<int> struct thing { using T = decltype([](auto) { }); static constexpr auto value = [](auto) { return get<T>(); }(0); }; thing<0> X; --- In this case template_parms_to_args() is called with a nullptr. template_parms_to_args (parms=0x0) at /usr/src/debug/gcc/gcc/cp/pt.cc:4912 tsubst_template_decl (t=0x7ffff7177280, args=<optimized out>, complain=3, lambda_fntype=0x7ffff717b738) at /usr/src/debug/gcc/gcc/cp/pt.cc:14543 tsubst_lambda_expr (t=<optimized out>, args=0x7ffff7171d80, complain=3, in_decl=0x7ffff7173800) at /usr/src/debug/gcc/gcc/cp/pt.cc:19855 tsubst_copy_and_build (t=<optimized out>, args=0x7ffff7171d80, complain=<optimized out>, in_decl=0x7ffff7177000, function_p=<optimized out>, integral_constant_expression_p=false) at /usr/src/debug/gcc/gcc/cp/pt.cc:21446 tsubst (t=0x7ffff71760a8, args=0x7ffff7171d80, complain=3, in_decl=0x7ffff7177000) at /usr/src/debug/gcc/gcc/cp/pt.cc:16400 tsubst_template_args (t=0x7ffff7171a20, args=args@entry=0x7ffff7171d80, complain=complain@entry=3, in_decl=in_decl@entry=0x7ffff7177000) at /usr/src/debug/gcc/gcc/cp/pt.cc:13580 [...] --- GCC 12.2.0, but GCC trunk on Compiler Explorer also exhibits the same issue (as do GCC 11.1, 11.2, 11.3, 12.1, and 12.2)
next prev parent reply other threads:[~2022-09-04 17:40 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 [this message] 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-uuJdwhwZja@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).