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++/99246] New: internal compiler error: in write_location, at cp/module.cc:15687 Date: Wed, 24 Feb 2021 08:49:00 +0000 [thread overview] Message-ID: <bug-99246-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99246 Bug ID: 99246 Summary: internal compiler error: in write_location, at cp/module.cc:15687 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 numbers g++ -std=c++20 -fmodules-ts -x c++-system-header ratio g++ -std=c++20 -fmodules-ts -x c++-system-header cstdio g++ -std=c++20 -fmodules-ts -x c++-system-header ostream g++ -std=c++20 -fmodules-ts -x c++-system-header coroutine g++ -std=c++20 -fmodules-ts -x c++-system-header barrier ---- /usr/local/include/c++/11.0.0/barrier: internal compiler error: in write_location, at cp/module.cc:15687 0x6ddcb3 module_state::write_location(bytes_out&, unsigned int) ../../gcc/gcc/cp/module.cc:15687 0xa5cbc9 trees_out::core_vals(tree_node*) ../../gcc/gcc/cp/module.cc:5912 0xa5dafc trees_out::tree_node_vals(tree_node*) ../../gcc/gcc/cp/module.cc:7166 0xa5dafc trees_out::fn_parms_init(tree_node*) ../../gcc/gcc/cp/module.cc:10067 0xa5aa96 trees_out::decl_value(tree_node*, depset*) ../../gcc/gcc/cp/module.cc:7763 0xa5b0bb trees_out::decl_node(tree_node*, walk_kind) ../../gcc/gcc/cp/module.cc:8624 0xa5c0b2 trees_out::tree_node(tree_node*) ../../gcc/gcc/cp/module.cc:9179 0xa611f0 module_state::write_cluster(elf_out*, depset**, unsigned int, depset::hash&, unsigned int*, unsigned int*) ../../gcc/gcc/cp/module.cc:14763 0xa62be8 module_state::write(elf_out*, cpp_reader*) ../../gcc/gcc/cp/module.cc:17734 0xa638fc finish_module_processing(cpp_reader*) ../../gcc/gcc/cp/module.cc:19860 0x9f72cb c_parse_final_cleanups() ../../gcc/gcc/cp/decl2.c:5175 ---- g++ (GCC) 11.0.0 20210223 (experimental)
next reply other threads:[~2021-02-24 8:49 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-24 8:49 alexander.lelyakin at googlemail dot com [this message] 2021-02-26 8:47 ` [Bug c++/99246] [modules] ICE " alexander.lelyakin at googlemail dot com 2021-02-26 12:49 ` nathan at gcc dot gnu.org 2021-03-24 10:04 ` alexander.lelyakin at googlemail dot com 2021-03-31 5:21 ` alexander.lelyakin at googlemail dot com 2021-04-14 15:19 ` cvs-commit at gcc dot gnu.org 2021-04-15 11:00 ` rsandifo 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-99246-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).