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++/99855] [modules] ICE Error reporting routines re-entered. Date: Wed, 31 Mar 2021 19:03:25 +0000 [thread overview] Message-ID: <bug-99855-4-vfB4mj6HOs@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99855-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99855 --- Comment #2 from Alexander Lelyakin <alexander.lelyakin at googlemail dot com> --- Yes, attempting to repeat gives different message, but not same as by you: malloc(): smallbin double linked list corrupted In file included from /usr/local/include/c++/11.0.1/bits/fs_path.h:46, from /usr/local/include/c++/11.0.1/filesystem:45: /usr/local/include/c++/11.0.1/bits/shared_ptr.h:330:32: internal compiler error: Aborted 330 | #pragma GCC diagnostic ignored "-Wdeprecated-declarations" | ^~~~~~~~~~~~~~~~~~~~~~~~~~~ 0x11016bf crash_signal ../../gcc/gcc/toplev.c:327 0x1d47750 xrealloc ../../gcc/libiberty/xmalloc.c:179 0x1cb82a7 diagnostic_classify_diagnostic(diagnostic_context*, int, diagnostic_t, unsigned int) ../../gcc/gcc/diagnostic.c:864 0x1ca85ca control_warning_option(unsigned int, int, char const*, bool, unsigned int, unsigned int, cl_option_handlers const*, gcc_options*, gcc_options*, diagnostic_context*) ../../gcc/gcc/opts-common.c:1722 0xc00249 handle_pragma_diagnostic ../../gcc/gcc/c-family/c-pragma.c:849 0xaa63ab cp_parser_pragma ../../gcc/gcc/cp/parser.c:45198 0xaa7f4e cp_parser_member_specification_opt ../../gcc/gcc/cp/parser.c:25793 0xaa7f4e cp_parser_class_specifier_1 ../../gcc/gcc/cp/parser.c:24877 0xaaa0a3 cp_parser_class_specifier ../../gcc/gcc/cp/parser.c:25193 0xaaa0a3 cp_parser_type_specifier ../../gcc/gcc/cp/parser.c:18440 0xaab039 cp_parser_decl_specifier_seq ../../gcc/gcc/cp/parser.c:15062 0xad5c46 cp_parser_single_declaration ../../gcc/gcc/cp/parser.c:30426 0xad5fc6 cp_parser_template_declaration_after_parameters ../../gcc/gcc/cp/parser.c:30089 0xad6770 cp_parser_explicit_template_declaration ../../gcc/gcc/cp/parser.c:30355 0xad8e99 cp_parser_declaration ../../gcc/gcc/cp/parser.c:14068 0xad8469 cp_parser_toplevel_declaration ../../gcc/gcc/cp/parser.c:14166 0xad8469 cp_parser_declaration_seq_opt ../../gcc/gcc/cp/parser.c:13954 0xad8902 cp_parser_namespace_body ../../gcc/gcc/cp/parser.c:20454 0xad8902 cp_parser_namespace_definition ../../gcc/gcc/cp/parser.c:20432 0xad9058 cp_parser_declaration ../../gcc/gcc/cp/parser.c:14117 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.
next prev parent reply other threads:[~2021-03-31 19:03 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-31 18:46 [Bug c++/99855] New: " alexander.lelyakin at googlemail dot com 2021-03-31 18:54 ` [Bug c++/99855] " mpolacek at gcc dot gnu.org 2021-03-31 19:03 ` alexander.lelyakin at googlemail dot com [this message] 2021-03-31 19:05 ` alexander.lelyakin at googlemail dot com 2021-03-31 19:07 ` alexander.lelyakin at googlemail dot com 2021-03-31 19:14 ` alexander.lelyakin at googlemail dot com 2021-04-01 6:12 ` alexander.lelyakin at googlemail dot com 2021-04-07 6:29 ` alexander.lelyakin at googlemail dot com
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-99855-4-vfB4mj6HOs@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).