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++/99480] New: [modules] ICE in import_entity_index, at cp/module.cc:3952 Date: Tue, 09 Mar 2021 07:39:39 +0000 [thread overview] Message-ID: <bug-99480-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99480 Bug ID: 99480 Summary: [modules] ICE in import_entity_index, at cp/module.cc:3952 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: --- g++ -std=c++20 -fmodules-ts -x c++-system-header memory g++ -std=c++20 -fmodules-ts -x c++-system-header execution ---- In file included from /usr/local/include/c++/11.0.1/pstl/parallel_impl.h:13, from /usr/local/include/c++/11.0.1/pstl/algorithm_impl.h:23, from /usr/local/include/c++/11.0.1/pstl/glue_execution_defs.h:50, from /usr/local/include/c++/11.0.1/execution:32: /usr/local/include/c++/11.0.1/atomic:415:5: internal compiler error: in import_entity_index, at cp/module.cc:3952 415 | { | ^ 0x6dbec6 import_entity_index ../../gcc/gcc/cp/module.cc:3952 0x6dbec6 import_entity_index ../../gcc/gcc/cp/module.cc:3947 0xa53bd2 module_may_redeclare(tree_node*) ../../gcc/gcc/cp/module.cc:18453 0xb49920 begin_class_definition(tree_node*) ../../gcc/gcc/cp/semantics.c:3269 0xaa5680 cp_parser_class_specifier_1 ../../gcc/gcc/cp/parser.c:24849 0xaa7c13 cp_parser_class_specifier ../../gcc/gcc/cp/parser.c:25172 0xaa7c13 cp_parser_type_specifier ../../gcc/gcc/cp/parser.c:18419 0xaa8ba9 cp_parser_decl_specifier_seq ../../gcc/gcc/cp/parser.c:15041 0xad3796 cp_parser_single_declaration ../../gcc/gcc/cp/parser.c:30402 0xad3b16 cp_parser_template_declaration_after_parameters ../../gcc/gcc/cp/parser.c:30065 0xad42c0 cp_parser_explicit_template_declaration ../../gcc/gcc/cp/parser.c:30331 0xad69e9 cp_parser_declaration ../../gcc/gcc/cp/parser.c:14047 0xad5fb9 cp_parser_toplevel_declaration ../../gcc/gcc/cp/parser.c:14145 0xad5fb9 cp_parser_declaration_seq_opt ../../gcc/gcc/cp/parser.c:13933 0xad6452 cp_parser_namespace_body ../../gcc/gcc/cp/parser.c:20433 0xad6452 cp_parser_namespace_definition ../../gcc/gcc/cp/parser.c:20411 0xad6ba8 cp_parser_declaration ../../gcc/gcc/cp/parser.c:14096 0xad73fc cp_parser_toplevel_declaration ../../gcc/gcc/cp/parser.c:14145 0xad73fc cp_parser_translation_unit ../../gcc/gcc/cp/parser.c:4936 0xad73fc c_parse_file() ../../gcc/gcc/cp/parser.c:45231 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 20210308 (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 reply other threads:[~2021-03-09 7:39 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-09 7:39 alexander.lelyakin at googlemail dot com [this message] 2021-03-22 16:04 ` [Bug c++/99480] " nathan at gcc dot gnu.org 2021-03-22 19:41 ` cvs-commit at gcc dot gnu.org 2021-03-22 19:42 ` nathan 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-99480-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: 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).