public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/100129] [modules] ICE free(): invalid pointer
Date: Thu, 30 Dec 2021 04:42:40 +0000	[thread overview]
Message-ID: <bug-100129-4-Tr77EOulqf@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100129-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Add --param=ggc-min-expand=1 we get:
hash table checking failed: equal operator returns true for a pair of values
with a different hash value
In file included from /home/apinski/upstream-gcc/include/c++/12.0.0/future:44:
/home/apinski/upstream-gcc/include/c++/12.0.0/bits/atomic_futex.h:76:5:
internal compiler error: in hashtab_chk_error, at hash-table.c:137
   76 |     atomic<unsigned> _M_data;
      |     ^~~~~~
0x9bab97 hashtab_chk_error()
        /home/apinski/src/upstream-gcc/gcc/gcc/hash-table.c:137
0xbd7e85 hash_table<spec_hasher, false, xcallocator>::verify(spec_entry*
const&, unsigned int)
        /home/apinski/src/upstream-gcc/gcc/gcc/hash-table.h:1036
0xbd840c hash_table<spec_hasher, false,
xcallocator>::find_slot_with_hash(spec_entry* const&, unsigned int,
insert_option)
        /home/apinski/src/upstream-gcc/gcc/gcc/hash-table.h:971
0xb93d0b match_mergeable_specialization(bool, spec_entry*)
        /home/apinski/src/upstream-gcc/gcc/gcc/cp/pt.c:30400
0xb0531c trees_in::key_mergeable(int, merge_kind, tree_node*, tree_node*,
tree_node*, tree_node*, bool)
        /home/apinski/src/upstream-gcc/gcc/gcc/cp/module.cc:10683
0xb0925e trees_in::decl_value()
        /home/apinski/src/upstream-gcc/gcc/gcc/cp/module.cc:7911
0xb02147 trees_in::tree_node(bool)
        /home/apinski/src/upstream-gcc/gcc/gcc/cp/module.cc:9164
0xb0864b module_state::read_cluster(unsigned int)
        /home/apinski/src/upstream-gcc/gcc/gcc/cp/module.cc:14830
0xb08be5 module_state::load_section(unsigned int, binding_slot*)
        /home/apinski/src/upstream-gcc/gcc/gcc/cp/module.cc:18101
0xb08d9e lazy_load_binding(unsigned int, tree_node*, tree_node*, binding_slot*)
        /home/apinski/src/upstream-gcc/gcc/gcc/cp/module.cc:18792
0xb1abed name_lookup::search_namespace_only(tree_node*)
        /home/apinski/src/upstream-gcc/gcc/gcc/cp/name-lookup.c:927
0xb1c0f3 name_lookup::search_unqualified(tree_node*, cp_binding_level*)
        /home/apinski/src/upstream-gcc/gcc/gcc/cp/name-lookup.c:1157
0xb1de2d lookup_name(tree_node*, LOOK_where, LOOK_want)
        /home/apinski/src/upstream-gcc/gcc/gcc/cp/name-lookup.c:7739
0xb2f229 lookup_name(tree_node*, LOOK_want)
        /home/apinski/src/upstream-gcc/gcc/gcc/cp/name-lookup.h:401
0xb2f229 cp_parser_lookup_name
        /home/apinski/src/upstream-gcc/gcc/gcc/cp/parser.c:30528
0xb5adf8 cp_parser_template_name
        /home/apinski/src/upstream-gcc/gcc/gcc/cp/parser.c:18539
0xb5b409 cp_parser_template_id
        /home/apinski/src/upstream-gcc/gcc/gcc/cp/parser.c:18143
0xb5bd6b cp_parser_class_name
        /home/apinski/src/upstream-gcc/gcc/gcc/cp/parser.c:25640
0xb5271e cp_parser_qualifying_entity
        /home/apinski/src/upstream-gcc/gcc/gcc/cp/parser.c:7061
0xb5271e cp_parser_nested_name_specifier_opt
        /home/apinski/src/upstream-gcc/gcc/gcc/cp/parser.c:6743
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.

I am going to assume this is the same bug when I reducing it but if it is not
then I will deal with it later.

  parent reply	other threads:[~2021-12-30  4:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-17  6:48 [Bug c++/100129] New: " alexander.lelyakin at googlemail dot com
2021-12-29 21:44 ` [Bug c++/100129] " pinskia at gcc dot gnu.org
2021-12-30  0:19 ` pinskia at gcc dot gnu.org
2021-12-30  4:42 ` pinskia at gcc dot gnu.org [this message]
2021-12-30  7:11 ` pinskia at gcc dot gnu.org
2021-12-30 16:10 ` pinskia at gcc dot gnu.org
2021-12-30 16:12 ` 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-100129-4-Tr77EOulqf@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).