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++/99245] [modules] ICE in write_cluster, at cp/module.cc:14600 Date: Sun, 28 Feb 2021 18:54:17 +0000 [thread overview] Message-ID: <bug-99245-4-zmbJASspMe@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99245-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99245 --- Comment #1 from Alexander Lelyakin <alexander.lelyakin at googlemail dot com> --- There is a shorter sequence: g++ -std=c++20 -fmodules-ts -x c++-system-header typeinfo g++ -std=c++20 -fmodules-ts -x c++-system-header ostream ---- /usr/local/include/c++/11.0.1/ostream: internal compiler error: in write_cluster, at cp/module.cc:14605 0x6e2d18 module_state::write_cluster(elf_out*, depset**, unsigned int, depset::hash&, unsigned int*, unsigned int*) ../../gcc/gcc/cp/module.cc:14605 0xa634de module_state::write(elf_out*, cpp_reader*) ../../gcc/gcc/cp/module.cc:17785 0xa640cf finish_module_processing(cpp_reader*) ../../gcc/gcc/cp/module.cc:19922 0x9f776b c_parse_final_cleanups() ../../gcc/gcc/cp/decl2.c:5175 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 20210228 (experimental)
next prev parent reply other threads:[~2021-02-28 18:54 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-24 8:47 [Bug c++/99245] New: internal compiler error: " alexander.lelyakin at googlemail dot com 2021-02-28 18:54 ` alexander.lelyakin at googlemail dot com [this message] 2021-03-05 19:51 ` [Bug c++/99245] [modules] ICE " nathan at gcc dot gnu.org 2021-03-05 20:54 ` cvs-commit at gcc dot gnu.org 2021-03-05 20:54 ` nathan at gcc dot gnu.org 2021-12-29 23:04 ` pinskia 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-99245-4-zmbJASspMe@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).