public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/94155] internal compiler error: in gimplify_init_ctor_eval, at gimplify.c:4664 Date: Fri, 27 Mar 2020 20:23:17 +0000 [thread overview] Message-ID: <bug-94155-4-pzd0d62VXS@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94155-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94155 --- Comment #2 from Marek Polacek <mpolacek at gcc dot gnu.org> --- Reduced: template <typename T> struct A { int i; T t; constexpr A(int, T e) : i(), t(e) {} }; void f() { A<A<int>> g[1]({1, {1, 1}}); } We ICE because we don't satisfy: 4662 /* ??? Here's to hoping the front end fills in all of the indices, 4663 so we don't have to figure out what's missing ourselves. */ 4664 gcc_assert (purpose);
next prev parent reply other threads:[~2020-03-27 20:23 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-12 13:34 [Bug c++/94155] New: " redi at gcc dot gnu.org 2020-03-12 13:35 ` [Bug c++/94155] " redi at gcc dot gnu.org 2020-03-12 14:07 ` mpolacek at gcc dot gnu.org 2020-03-27 20:23 ` mpolacek at gcc dot gnu.org [this message] 2020-03-27 21:17 ` mpolacek at gcc dot gnu.org 2020-04-06 16:39 ` cvs-commit at gcc dot gnu.org 2020-04-06 16:40 ` mpolacek 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-94155-4-pzd0d62VXS@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).