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++/99861] [modules] ICE in hashtab_chk_error
Date: Fri, 16 Apr 2021 13:05:17 +0000	[thread overview]
Message-ID: <bug-99861-4-7is6l27OPF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99861-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #9 from Alexander Lelyakin <alexander.lelyakin at googlemail dot com> ---
The same happens with the ICE in add_mergeable_specialization, PR99948,
http://lelyakin.de/modules/in%20add_mergeable_specialization/016_7ae8737cc3d793d796faedfe5de5d89d42b966b5/

After adding parameter --param=hash-table-verification-limit=1000
the error was transformed to:

hash table checking failed: equal operator returns true for a pair of values
with a different hash value
In file included from /usr/local/include/c++/11.0.1/memory:68,
                 from /usr/local/include/c++/11.0.1/regex:45:
/usr/local/include/c++/11.0.1/bits/stl_raw_storage_iter.h: In destructor
‘constexpr std::allocator< <template-parameter-1-1> >::~allocator() [with _Tp =
char32_t]’:
/usr/local/include/c++/11.0.1/bits/stl_raw_storage_iter.h:95:58: internal
compiler error: in hashtab_chk_error, at hash-table.c:137
   95 |         std::_Construct(std::__addressof(*_M_iter),
std::move(__element));
      |                                                          ^~~~
0x92f671 hashtab_chk_error()
        ../../gcc/gcc/hash-table.c:137
0xb3ec35 hash_table<spec_hasher, false, xcallocator>::verify(spec_entry*
const&, unsigned int)
        ../../gcc/gcc/hash-table.h:1033
0xb3f1be hash_table<spec_hasher, false,
xcallocator>::find_slot_with_hash(spec_entry* const&, unsigned int,
insert_option)
        ../../gcc/gcc/hash-table.h:968
0xafbd2b match_mergeable_specialization(bool, spec_entry*)
        ../../gcc/gcc/cp/pt.c:30034
0xa74e18 trees_in::key_mergeable(int, merge_kind, tree_node*, tree_node*,
tree_node*, tree_node*, bool)
        ../../gcc/gcc/cp/module.cc:10670
0xa78a14 trees_in::decl_value()
        ../../gcc/gcc/cp/module.cc:7903
0xa71877 trees_in::tree_node(bool)
        ../../gcc/gcc/cp/module.cc:9153
0xa77e9b module_state::read_cluster(unsigned int)
        ../../gcc/gcc/cp/module.cc:14811
0xa7839d module_state::load_section(unsigned int, binding_slot*)
        ../../gcc/gcc/cp/module.cc:18082
0xa7845f module_state::lazy_load(unsigned int, binding_slot*)
        ../../gcc/gcc/cp/module.cc:18740
0xa726e0 trees_in::tree_node(bool)
        ../../gcc/gcc/cp/module.cc:9664
0xa77b9b module_state::read_cluster(unsigned int)
        ../../gcc/gcc/cp/module.cc:14717
0xa7839d module_state::load_section(unsigned int, binding_slot*)
        ../../gcc/gcc/cp/module.cc:18082
0xa7845f module_state::lazy_load(unsigned int, binding_slot*)
        ../../gcc/gcc/cp/module.cc:18740
0xa726e0 trees_in::tree_node(bool)
        ../../gcc/gcc/cp/module.cc:9664
0xa77b9b module_state::read_cluster(unsigned int)
        ../../gcc/gcc/cp/module.cc:14717
0xa7839d module_state::load_section(unsigned int, binding_slot*)
        ../../gcc/gcc/cp/module.cc:18082
0xa7845f module_state::lazy_load(unsigned int, binding_slot*)
        ../../gcc/gcc/cp/module.cc:18740
0xa7b5b7 lazy_load_pendings(tree_node*)
        ../../gcc/gcc/cp/module.cc:18833
0xa83d58 maybe_lazily_declare
        ../../gcc/gcc/cp/name-lookup.c:1912
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.

However this parameter significantly slows compilation.

And already two weeks this report remains unassigned...

  parent reply	other threads:[~2021-04-16 13:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-01  4:51 [Bug c++/99861] New: " alexander.lelyakin at googlemail dot com
2021-04-01  7:49 ` [Bug c++/99861] " marxin at gcc dot gnu.org
2021-04-01  7:50 ` marxin at gcc dot gnu.org
2021-04-05 11:20 ` alexander.lelyakin at googlemail dot com
2021-04-09 16:28 ` alexander.lelyakin at googlemail dot com
2021-04-15 17:15 ` alexander.lelyakin at googlemail dot com
2021-04-16  7:19 ` marxin at gcc dot gnu.org
2021-04-16 11:44 ` alexander.lelyakin at googlemail dot com
2021-04-16 11:52 ` marxin at gcc dot gnu.org
2021-04-16 12:35 ` alexander.lelyakin at googlemail dot com
2021-04-16 13:05 ` alexander.lelyakin at googlemail dot com [this message]
2021-12-30 16:11 ` pinskia at gcc dot gnu.org
2021-12-30 16:12 ` pinskia at gcc dot gnu.org
2021-12-30 16:18 ` pinskia at gcc dot gnu.org
2021-12-30 16:20 ` pinskia at gcc dot gnu.org
2022-01-01  4:19 ` 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-99861-4-7is6l27OPF@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).