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++/99737] [modules] malloc(): smallbin double linked list corrupted Date: Sat, 27 Mar 2021 12:23:59 +0000 [thread overview] Message-ID: <bug-99737-4-J9opLicZOB@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99737-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99737 --- Comment #1 from Alexander Lelyakin <alexander.lelyakin at googlemail dot com> --- Similar, but somewhat different message: /usr/local/bin/g++ -std=c++20 -fmodules-ts -x c++-system-header cwchar /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 type_traits /usr/local/bin/g++ -std=c++20 -fmodules-ts -x c++-system-header condition_variable /usr/local/bin/g++ -std=c++20 -fmodules-ts -x c++-system-header future ---- corrupted double-linked list In file included from /usr/local/include/c++/11.0.1/future:43: /usr/local/include/c++/11.0.1/bits/atomic_futex.h:171:36: internal compiler error: Aborted 171 | bool __equal, memory_order __mo, | ^~~~ 0x110151f crash_signal ../../gcc/gcc/toplev.c:327 0x1d474c4 xcalloc ../../gcc/libiberty/xmalloc.c:162 0xc2d30c alloc_page ../../gcc/gcc/ggc-page.c:918 0xc2d30c ggc_internal_alloc(unsigned long, void (*)(void*), unsigned long, unsigned long) ../../gcc/gcc/ggc-page.c:1294 0xe16c69 ggc_internal_cleared_alloc(unsigned long, void (*)(void*), unsigned long, unsigned long) ../../gcc/gcc/ggc-common.c:117 0xa25f78 ggc_internal_cleared_alloc(unsigned long) ../../gcc/gcc/ggc.h:143 0xa25f78 maybe_add_lang_decl_raw(tree_node*, bool) ../../gcc/gcc/cp/lex.c:903 0xa2626e retrofit_lang_decl(tree_node*) ../../gcc/gcc/cp/lex.c:972 0xa2626e retrofit_lang_decl(tree_node*) ../../gcc/gcc/cp/lex.c:967 0xac6725 cp_parser_parameter_declaration_list ../../gcc/gcc/cp/parser.c:23607 0xac6ab1 cp_parser_parameter_declaration_clause ../../gcc/gcc/cp/parser.c:23496 0xab7be3 cp_parser_direct_declarator ../../gcc/gcc/cp/parser.c:22145 0xab7be3 cp_parser_declarator ../../gcc/gcc/cp/parser.c:22008 0xacee48 cp_parser_init_declarator ../../gcc/gcc/cp/parser.c:21506 0xad5c7b cp_parser_single_declaration ../../gcc/gcc/cp/parser.c:30517 0xad5de6 cp_parser_template_declaration_after_parameters ../../gcc/gcc/cp/parser.c:30089 0xad6590 cp_parser_explicit_template_declaration ../../gcc/gcc/cp/parser.c:30355 0xaa7998 cp_parser_member_specification_opt ../../gcc/gcc/cp/parser.c:25799 0xaa7998 cp_parser_class_specifier_1 ../../gcc/gcc/cp/parser.c:24877 0xaa9ec3 cp_parser_class_specifier ../../gcc/gcc/cp/parser.c:25193 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 20210327 (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.
next prev parent reply other threads:[~2021-03-27 12:24 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-23 20:14 [Bug c++/99737] New: " alexander.lelyakin at googlemail dot com 2021-03-27 12:23 ` alexander.lelyakin at googlemail dot com [this message] 2021-03-27 19:44 ` [Bug c++/99737] " alexander.lelyakin at googlemail dot com 2021-03-27 19:50 ` alexander.lelyakin at googlemail dot com 2021-04-01 5:30 ` alexander.lelyakin at googlemail dot com 2021-12-30 16:09 ` pinskia at gcc dot gnu.org 2024-03-07 19:56 ` 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-99737-4-J9opLicZOB@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: linkBe 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).