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] New: [modules] ICE in hashtab_chk_error
Date: Thu, 01 Apr 2021 04:51:19 +0000	[thread overview]
Message-ID: <bug-99861-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 99861
           Summary: [modules] ICE in hashtab_chk_error
           Product: gcc
           Version: 11.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: alexander.lelyakin at googlemail dot com
  Target Milestone: ---

/usr/local/bin/g++ -std=c++20 -fmodules-ts -x c++-system-header latch
/usr/local/bin/g++ -std=c++20 -fmodules-ts -x c++-system-header cfenv
/usr/local/bin/g++ -std=c++20 -fmodules-ts -x c++-system-header clocale
/usr/local/bin/g++ -std=c++20 -fmodules-ts -x c++-system-header cmath
/usr/local/bin/g++ -std=c++20 -fmodules-ts -x c++-system-header ciso646
/usr/local/bin/g++ -std=c++20 -fmodules-ts -x c++-system-header unordered_map
/usr/local/bin/g++ -std=c++20 -fmodules-ts -x c++-system-header algorithm
----
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/vector:66,
                 from /usr/local/include/c++/11.0.1/functional:62,
                 from
/usr/local/include/c++/11.0.1/pstl/glue_algorithm_defs.h:13,
                 from /usr/local/include/c++/11.0.1/algorithm:74:
/usr/local/include/c++/11.0.1/bits/stl_uninitialized.h: In static member
function ‘static _ForwardIterator
std::__uninitialized_copy<true>::__uninit_copy(_InputIterator, _InputIterator,
_ForwardIterator)’:
/usr/local/include/c++/11.0.1/bits/stl_uninitialized.h:110:23: internal
compiler error: in hashtab_chk_error, at hash-table.c:137
  110 |         { return std::copy(__first, __last, __result); }
      |                       ^~~~
0x92894b hashtab_chk_error()
        ../../gcc/gcc/hash-table.c:137
0xb35fa5 hash_table<spec_hasher, false, xcallocator>::verify(spec_entry*
const&, unsigned int)
        ../../gcc/gcc/hash-table.h:1033
0xb3652e hash_table<spec_hasher, false,
xcallocator>::find_slot_with_hash(spec_entry* const&, unsigned int,
insert_option)
        ../../gcc/gcc/hash-table.h:968
0xaf315b match_mergeable_specialization(bool, spec_entry*)
        ../../gcc/gcc/cp/pt.c:29942
0xa6cf43 trees_in::key_mergeable(int, merge_kind, tree_node*, tree_node*,
tree_node*, tree_node*, bool)
        ../../gcc/gcc/cp/module.cc:10667
0xa70564 trees_in::decl_value()
        ../../gcc/gcc/cp/module.cc:7899
0xa693c7 trees_in::tree_node(bool)
        ../../gcc/gcc/cp/module.cc:9150
0xa6f9eb module_state::read_cluster(unsigned int)
        ../../gcc/gcc/cp/module.cc:14797
0xa6feed module_state::load_section(unsigned int, binding_slot*)
        ../../gcc/gcc/cp/module.cc:18068
0xa6ffaf module_state::lazy_load(unsigned int, binding_slot*)
        ../../gcc/gcc/cp/module.cc:18726
0xa6a230 trees_in::tree_node(bool)
        ../../gcc/gcc/cp/module.cc:9661
0xa6b046 trees_in::core_vals(tree_node*)
        ../../gcc/gcc/cp/module.cc:6662
0xa68a97 trees_in::tree_node_vals(tree_node*)
        ../../gcc/gcc/cp/module.cc:7057
0xa68a97 trees_in::tree_value()
        ../../gcc/gcc/cp/module.cc:8927
0xa68ecf trees_in::tree_node(bool)
        ../../gcc/gcc/cp/module.cc:9145
0xa6acd1 trees_in::core_vals(tree_node*)
        ../../gcc/gcc/cp/module.cc:6413
0xa68a97 trees_in::tree_node_vals(tree_node*)
        ../../gcc/gcc/cp/module.cc:7057
0xa68a97 trees_in::tree_value()
        ../../gcc/gcc/cp/module.cc:8927
0xa68ecf trees_in::tree_node(bool)
        ../../gcc/gcc/cp/module.cc:9145
0xa6acd1 trees_in::core_vals(tree_node*)
        ../../gcc/gcc/cp/module.cc:6413
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 20210331 (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.

             reply	other threads:[~2021-04-01  4:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-01  4:51 alexander.lelyakin at googlemail dot com [this message]
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
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@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).