public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "unlvsur at live dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/103994] New: Module ICE in mark_by_value, at cp/module.cc:4772 Date: Wed, 12 Jan 2022 16:56:18 +0000 [thread overview] Message-ID: <bug-103994-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103994 Bug ID: 103994 Summary: Module ICE in mark_by_value, at cp/module.cc:4772 Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: unlvsur at live dot com Target Milestone: --- Created attachment 52172 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52172&action=edit module ICE module; #include <gtirb/gtirb.hpp> export module cfg; namespace cfg { export struct cfg_vertex { gtirb::CfgNode const* cfg_node_ptr{}; struct edge { std::size_t to{}; gtirb::CfgNode const* cfg_node_ptr{}; }; std::vector<edge> edges; }; export inline std::vector<cfg_vertex> get_cfg() { return {}; } } g++ -c cfg.cc -O2 -std=c++20 -fmodules-ts cfg.cc:5:8: internal compiler error: in mark_by_value, at cp/module.cc:4772 5 | export module cfg; | ^ 0x7f8092e45fcf __libc_start_call_main ../sysdeps/nptl/libc_start_call_main.h:58 0x7f8092e4607c __libc_start_main_impl ../csu/libc-start.c:409
next reply other threads:[~2022-01-12 16:56 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-12 16:56 unlvsur at live dot com [this message] 2022-10-18 12:59 ` [Bug c++/103994] Module ICE in write_var_def with global variable in global module fragment ppalka at gcc dot gnu.org 2023-02-01 17:33 ` Melven.Roehrig-Zoellner at DLR dot de 2024-01-27 16:10 ` ppalka at gcc dot gnu.org 2024-01-27 16:15 ` ppalka at gcc dot gnu.org 2024-03-04 16:02 ` ppalka at gcc dot gnu.org 2024-03-07 21:39 ` cvs-commit at gcc dot gnu.org 2024-03-07 21:40 ` ppalka 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-103994-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).