public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hstong at ca dot ibm.com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/94100] ICE: tree check: accessed elt 1 of 'tree_vec' with 0 elts in tsubst_pack_expansion, at cp/pt.c:12765 Date: Thu, 02 Jul 2020 23:12:41 +0000 [thread overview] Message-ID: <bug-94100-4-N7GxehzvTD@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94100-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94100 --- Comment #2 from Hubert Tong <hstong at ca dot ibm.com> --- The following ICEs in a similar fashion: internal compiler error: tree check: accessed elt 2 of 'tree_vec' with 1 elts in tsubst, at cp/pt.c:15334 ### SOURCE: template <typename... T> struct ValListWithTypes { template <T... Members> struct WithVals { using TypeList = ValListWithTypes; }; }; template <typename ValList, typename ValTypeList = typename ValList::TypeList> struct Widget; template <typename ValList, typename... ValTypes> struct Widget<ValList, ValListWithTypes<ValTypes...>> { template <typename = ValList> struct Impl {}; }; template <typename ValList, typename... ValTypes> template <ValTypes... Vals> struct Widget<ValList, ValListWithTypes<ValTypes...>>::Impl< typename ValListWithTypes<ValTypes...>::template WithVals<Vals...>> {}; int main(void) { Widget<ValListWithTypes<int>::WithVals<0>>::Impl<> impl; }
prev parent reply other threads:[~2020-07-02 23:12 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-09 12:51 [Bug c++/94100] New: " jjk at acm dot org 2020-03-09 14:24 ` [Bug c++/94100] " mpolacek at gcc dot gnu.org 2020-07-02 23:12 ` hstong at ca dot ibm.com [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-94100-4-N7GxehzvTD@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).