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++/99239] New: [modules] internal compiler error: in duplicate_decls Date: Wed, 24 Feb 2021 08:37:49 +0000 [thread overview] Message-ID: <bug-99239-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99239 Bug ID: 99239 Summary: [modules] internal compiler error: in duplicate_decls 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 cstdio g++ -std=c++20 -fmodules-ts -x c++-system-header string g++ -std=c++20 -fmodules-ts -x c++-system-header filesystem ----- In file included from /usr/local/include/c++/11.0.0/bits/functexcept.h:40, from /usr/local/include/c++/11.0.0/bits/stl_algobase.h:60, from /usr/local/include/c++/11.0.0/bits/char_traits.h:39, from /usr/local/include/c++/11.0.0/string:40, of module /usr/local/include/c++/11.0.0/string, imported at /usr/local/include/c++/11.0.0/stdexcept:39, included from /usr/local/include/c++/11.0.0/system_error:41, from /usr/local/include/c++/11.0.0/bits/fs_fwd.h:35, from /usr/local/include/c++/11.0.0/filesystem:44: /usr/local/include/c++/11.0.0/bits/locale_classes.h:461:11: internal compiler error: in duplicate_decls, at cp/decl.c:2023 461 | __catch(...) | ^~~~~~~ 0x6b37fc duplicate_decls(tree_node*, tree_node*, bool, bool) ../../gcc/gcc/cp/decl.c:2023 0xa83ceb check_module_override ../../gcc/gcc/cp/name-lookup.c:3615 0xa83ceb do_pushdecl ../../gcc/gcc/cp/name-lookup.c:3734 0xa848d1 do_pushdecl ../../gcc/gcc/cp/name-lookup.c:4851 0xa848d1 do_pushdecl_with_scope ../../gcc/gcc/cp/name-lookup.c:4851 0xa84b02 pushdecl_namespace_level(tree_node*, bool) ../../gcc/gcc/cp/name-lookup.c:6213 0xa85bf4 pushdecl_top_level(tree_node*) ../../gcc/gcc/cp/name-lookup.c:8675 0xa072b2 declare_library_fn ../../gcc/gcc/cp/except.c:172 0xa07e9d do_end_catch ../../gcc/gcc/cp/except.c:254 0xa07e9d push_eh_cleanup ../../gcc/gcc/cp/except.c:270 0xa07e9d expand_start_catch_block(tree_node*) ../../gcc/gcc/cp/except.c:408 0xb42764 finish_handler_parms(tree_node*, tree_node*) ../../gcc/gcc/cp/semantics.c:1526 0xac95a3 cp_parser_handler ../../gcc/gcc/cp/parser.c:27094 0xaa9bd7 cp_parser_handler_seq ../../gcc/gcc/cp/parser.c:27069 0xaa9bd7 cp_parser_try_block ../../gcc/gcc/cp/parser.c:27023 0xaa9bd7 cp_parser_statement ../../gcc/gcc/cp/parser.c:11654 0xaaaf3d cp_parser_statement_seq_opt ../../gcc/gcc/cp/parser.c:12112 0xaab018 cp_parser_compound_statement ../../gcc/gcc/cp/parser.c:12062 0xacaf9d cp_parser_implicitly_scoped_statement ../../gcc/gcc/cp/parser.c:13568 0xaaa65d cp_parser_selection_statement ../../gcc/gcc/cp/parser.c:12290 ---- g++ (GCC) 11.0.0 20210223 (experimental)
next reply other threads:[~2021-02-24 8:37 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-24 8:37 alexander.lelyakin at googlemail dot com [this message] 2021-03-09 7:53 ` [Bug c++/99239] " alexander.lelyakin at googlemail dot com 2021-03-09 8:16 ` alexander.lelyakin at googlemail dot com 2021-03-23 12:21 ` cvs-commit at gcc dot gnu.org 2021-03-23 12:22 ` 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-99239-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).