public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "alexander.lelyakin at googlemail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/99248] [modules] ICE expected binding_vector, have overload in lookup_elaborated_type_1, at cp/name-lookup.c:8013
Date: Thu, 11 Mar 2021 08:12:47 +0000	[thread overview]
Message-ID: <bug-99248-4-cGL1jzXxEu@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99248-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Alexander Lelyakin <alexander.lelyakin at googlemail dot com> ---
There is much shorter sequence in last version 20210310:

g++ -std=c++20 -fmodules-ts -x c++-system-header streambuf
g++ -std=c++20 -fmodules-ts -x c++-system-header istream
----
In file included from /usr/local/include/c++/11.0.1/bits/locale_facets.h:2682,
                 from /usr/local/include/c++/11.0.1/bits/basic_ios.h:37,
                 from /usr/local/include/c++/11.0.1/ios:44,
                 from /usr/local/include/c++/11.0.1/istream:38:
/usr/local/include/c++/11.0.1/bits/locale_facets.tcc:42:12: internal compiler
error: tree check: expected binding_vector, have overload in
lookup_elaborated_type_1, at cp/name-lookup.c:7943
   42 |     struct __use_cache
      |            ^~~~~~~~~~~
0x875bfa tree_check_failed(tree_node const*, char const*, int, char const*,
...)
        ../../gcc/gcc/tree.c:9816
0x6eb804 tree_check(tree_node*, char const*, int, char const*, tree_code)
        ../../gcc/gcc/tree.h:3353
0x6eb804 lookup_elaborated_type_1
        ../../gcc/gcc/cp/name-lookup.c:7943
0x6eb804 lookup_elaborated_type(tree_node*, TAG_how)
        ../../gcc/gcc/cp/name-lookup.c:8034
0x9c5385 lookup_and_check_tag
        ../../gcc/gcc/cp/decl.c:15080
0x9c5741 xref_tag_1
        ../../gcc/gcc/cp/decl.c:15194
0x9c5c90 xref_tag(tag_types, tree_node*, TAG_how, bool)
        ../../gcc/gcc/cp/decl.c:15327
0xaa75c2 cp_parser_class_head
        ../../gcc/gcc/cp/parser.c:25586
0xaa75c2 cp_parser_class_specifier_1
        ../../gcc/gcc/cp/parser.c:24803
0xaa7f23 cp_parser_class_specifier
        ../../gcc/gcc/cp/parser.c:25182
0xaa7f23 cp_parser_type_specifier
        ../../gcc/gcc/cp/parser.c:18429
0xaa8eb9 cp_parser_decl_specifier_seq
        ../../gcc/gcc/cp/parser.c:15051
0xad3a76 cp_parser_single_declaration
        ../../gcc/gcc/cp/parser.c:30412
0xad3df6 cp_parser_template_declaration_after_parameters
        ../../gcc/gcc/cp/parser.c:30075
0xad45a0 cp_parser_explicit_template_declaration
        ../../gcc/gcc/cp/parser.c:30341
0xad6cc9 cp_parser_declaration
        ../../gcc/gcc/cp/parser.c:14057
0xad6299 cp_parser_toplevel_declaration
        ../../gcc/gcc/cp/parser.c:14155
0xad6299 cp_parser_declaration_seq_opt
        ../../gcc/gcc/cp/parser.c:13943
0xad6732 cp_parser_namespace_body
        ../../gcc/gcc/cp/parser.c:20443
0xad6732 cp_parser_namespace_definition
        ../../gcc/gcc/cp/parser.c:20421
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
----
g++ (GCC) 11.0.1 20210310 (experimental)
Copyright (C) 2021 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

  parent reply	other threads:[~2021-03-11  8:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-24  8:51 [Bug c++/99248] New: internal compiler error: tree check: " alexander.lelyakin at googlemail dot com
2021-02-28 21:00 ` [Bug c++/99248] [modules] ICE " alexander.lelyakin at googlemail dot com
2021-03-11  8:12 ` alexander.lelyakin at googlemail dot com [this message]
2021-03-11 19:52 ` nathan at gcc dot gnu.org
2021-03-11 21:13 ` cvs-commit at gcc dot gnu.org
2021-03-11 21:13 ` nathan 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-99248-4-cGL1jzXxEu@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).