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++/99426] [modules] failed to read compiled module cluster 1186: Bad file data
Date: Tue, 09 Mar 2021 15:56:07 +0000	[thread overview]
Message-ID: <bug-99426-4-P3X6DAOrr5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99426-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 from Alexander Lelyakin <alexander.lelyakin at googlemail dot com> ---
in version 20210308 diagnostic changed:
In file included from /usr/local/include/c++/11.0.1/iomanip:45:
/usr/local/include/c++/11.0.1/bits/quoted_string.h: In destructor ‘constexpr
std::allocator< <template-parameter-1-1> >::~allocator() [with _Tp =
char32_t]’:
/usr/local/include/c++/11.0.1/bits/quoted_string.h:69:29: internal compiler
error: tree check: expected template_decl, have function_decl in decl_value, at
cp/module.cc:7938
   69 |       struct _Quoted_string<basic_string_view<_CharT, _Traits>, _CharT>
      |                             ^~~~~~~~~~~~~~~~~
0x875ba8 tree_check_failed(tree_node const*, char const*, int, char const*,
...)
        ../../gcc/gcc/tree.c:9814
0x6e61c9 tree_check(tree_node*, char const*, int, char const*, tree_code)
        ../../gcc/gcc/tree.h:3353
0x6e61c9 trees_in::decl_value()
        ../../gcc/gcc/cp/module.cc:7938
0xa66d17 trees_in::tree_node(bool)
        ../../gcc/gcc/cp/module.cc:9174
0xa6d36b module_state::read_cluster(unsigned int)
        ../../gcc/gcc/cp/module.cc:14858
0xa6d86d module_state::load_section(unsigned int, binding_slot*)
        ../../gcc/gcc/cp/module.cc:18125
0xa6d92f module_state::lazy_load(unsigned int, binding_slot*)
        ../../gcc/gcc/cp/module.cc:18779
0xa70b67 lazy_load_pendings(tree_node*)
        ../../gcc/gcc/cp/module.cc:18872
0xa79448 maybe_lazily_declare
        ../../gcc/gcc/cp/name-lookup.c:1922
0xa79448 get_class_binding(tree_node*, tree_node*, bool)
        ../../gcc/gcc/cp/name-lookup.c:1958
0xb3c3be lookup_field_r
        ../../gcc/gcc/cp/search.c:1023
0xb3c646 dfs_walk_all(tree_node*, tree_node* (*)(tree_node*, void*), tree_node*
(*)(tree_node*, void*), void*)
        ../../gcc/gcc/cp/search.c:1453
0xb3c646 lookup_member(tree_node*, tree_node*, int, bool, int,
access_failure_info*)
        ../../gcc/gcc/cp/search.c:1166
0xa759c5 get_class_binding
        ../../gcc/gcc/cp/name-lookup.c:5327
0xa7cebf outer_binding(tree_node*, cxx_binding*, bool)
        ../../gcc/gcc/cp/name-lookup.c:7641
0xa8182a check_local_shadow
        ../../gcc/gcc/cp/name-lookup.c:3143
0xa85d8b do_pushdecl
        ../../gcc/gcc/cp/name-lookup.c:3767
0xa872d2 do_pushdecl
        ../../gcc/gcc/cp/name-lookup.c:3846
0xa872d2 pushdecl(tree_node*, bool)
        ../../gcc/gcc/cp/name-lookup.c:3846
0x9c61f1 do_push_parm_decls(tree_node*, tree_node*, tree_node**)
        ../../gcc/gcc/cp/decl.c:16847
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.

  reply	other threads:[~2021-03-09 15:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-06  7:54 [Bug c++/99426] New: " alexander.lelyakin at googlemail dot com
2021-03-09 15:56 ` alexander.lelyakin at googlemail dot com [this message]
2021-03-12  5:40 ` [Bug c++/99426] " alexander.lelyakin at googlemail dot com
2021-03-24 19:38 ` alexander.lelyakin at googlemail dot com
2021-03-30  1:34 ` mpolacek at gcc dot gnu.org
2021-03-30  6:50 ` alexander.lelyakin at googlemail dot com
2022-09-08  4:39 ` markmigm at gmail dot com
2024-02-27  2:15 ` ppalka at gcc dot gnu.org
2024-02-29 18:04 ` ppalka at gcc dot gnu.org
2024-04-03 21:19 ` ppalka at gcc dot gnu.org
2024-04-07 12:33 ` nickbegg at gmail dot com
2024-04-07 14:56 ` ppalka at gcc dot gnu.org
2024-04-07 20:49 ` nickbegg at gmail dot com
2024-04-12 19:52 ` ppalka at gcc dot gnu.org
2024-04-12 19:53 ` ppalka 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-99426-4-P3X6DAOrr5@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).