public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hewillk at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/99811] New: ICE: tree check: accessed elt 2 of 'tree_vec' with 1 elts in tsubst_pack_expansion, at cp/pt.c:13002
Date: Mon, 29 Mar 2021 07:57:03 +0000	[thread overview]
Message-ID: <bug-99811-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99811

            Bug ID: 99811
           Summary: ICE: tree check: accessed elt 2 of 'tree_vec' with 1
                    elts in tsubst_pack_expansion, at cp/pt.c:13002
           Product: gcc
           Version: 11.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: hewillk at gmail dot com
  Target Milestone: ---

https://godbolt.org/z/shj7Tr65M

related to PR 99809:

#include <concepts>

template <typename... Ts>
auto f(Ts...) {
  return []<typename... Us>(std::same_as<Ts> auto...) {};
}

int main() {
  f(0, 0.5)();
}

<source>:9:12: internal compiler error: tree check: accessed elt 2 of
'tree_vec' with 1 elts in tsubst_pack_expansion, at cp/pt.c:13002
    9 |   f(0, 0.5)();
      |   ~~~~~~~~~^~
0x1cfb7f9 internal_error(char const*, ...)
        ???:0
0x67bcb2 tree_vec_elt_check_failed(int, int, char const*, int, char const*)
        ???:0
0x93095c tsubst_pack_expansion(tree_node*, tree_node*, int, tree_node*)
        ???:0
0x73efca constraints_satisfied_p(tree_node*, tree_node*)
        ???:0
0x954963 fn_type_unification(tree_node*, tree_node*, tree_node*, tree_node*
const*, unsigned int, tree_node*, unification_kind_t, int, conversion**, bool,
bool)
        ???:0
0x6e225e build_op_call(tree_node*, vec<tree_node*, va_gc, vl_embed>**, int)
        ???:0
0x980ae5 finish_call_expr(tree_node*, vec<tree_node*, va_gc, vl_embed>**, bool,
bool, int)
        ???:0
0x8e12ad c_parse_file()
        ???:0
0xa600a2 c_common_parse_file()
        ???:0
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.

             reply	other threads:[~2021-03-29  7:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-29  7:57 hewillk at gmail dot com [this message]
2021-03-29  8:10 ` [Bug c++/99811] " hewillk at gmail dot com
2021-09-20 22:37 ` pinskia at gcc dot gnu.org
2021-12-14  8:04 ` pinskia at gcc dot gnu.org
2021-12-14  8:07 ` pinskia at gcc dot gnu.org
2021-12-14  8:10 ` pinskia at gcc dot gnu.org
2022-02-01 12:48 ` marxin at gcc dot gnu.org
2022-02-02  4:42 ` 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-99811-4@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).