public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "karl.weber99 at gmx dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/107083] New: internal compiler error: in core_vals, at cp/module.cc:6127 Date: Thu, 29 Sep 2022 09:26:33 +0000 [thread overview] Message-ID: <bug-107083-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107083 Bug ID: 107083 Summary: internal compiler error: in core_vals, at cp/module.cc:6127 Product: gcc Version: 12.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: karl.weber99 at gmx dot net Target Milestone: --- Created attachment 53639 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53639&action=edit Output of compiler due to option -freport-bug Environment: openSUSE 15.3 linux system. I downloaded fmt::format from https://github.com/fmtlib/fmt/ and tried to compile the header file fmt/core.h of this package with g++ -freport-bug -fmodules-ts -std=c++20 -c -x c++-system-header fmt/core.h The output of the compiler is /usr/local/include/fmt/core.h: internal compiler error: in core_vals, at cp/module.cc:6127 0x407d0d trees_out::core_vals(tree_node*) ../../gcc_12.2/gcc-12.2.0/gcc/cp/module.cc:6127 0x54143b trees_out::tree_node_vals(tree_node*) ../../gcc_12.2/gcc-12.2.0/gcc/cp/module.cc:7073 0x54143b trees_out::tree_value(tree_node*) ../../gcc_12.2/gcc-12.2.0/gcc/cp/module.cc:8910 0x53a43c trees_out::tree_node(tree_node*) ../../gcc_12.2/gcc-12.2.0/gcc/cp/module.cc:9108 0x53ddf5 trees_out::core_vals(tree_node*) ../../gcc_12.2/gcc-12.2.0/gcc/cp/module.cc:6036 0x53e460 trees_out::tree_node_vals(tree_node*) ../../gcc_12.2/gcc-12.2.0/gcc/cp/module.cc:7073 0x53f35b trees_out::decl_value(tree_node*, depset*) ../../gcc_12.2/gcc-12.2.0/gcc/cp/module.cc:7652 0x53f9f1 depset::hash::find_dependencies(module_state*) ../../gcc_12.2/gcc-12.2.0/gcc/cp/module.cc:13139 0x53ff86 module_state::write(elf_out*, cpp_reader*) ../../gcc_12.2/gcc-12.2.0/gcc/cp/module.cc:17629 0x541290 finish_module_processing(cpp_reader*) ../../gcc_12.2/gcc-12.2.0/gcc/cp/module.cc:19886 0x4ed14b c_parse_final_cleanups() ../../gcc_12.2/gcc-12.2.0/gcc/cp/decl2.cc:5342 Please submit a full bug report, with preprocessed source. Please include the complete backtrace with any bug report. See <https://gcc.gnu.org/bugs/> for instructions. Preprocessed source stored into /tmp/cc9Z23Fg.out file, please attach this to your bugreport.
next reply other threads:[~2022-09-29 9:26 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-29 9:26 karl.weber99 at gmx dot net [this message] 2022-09-30 15:23 ` [Bug c++/107083] [modules] " alexander.lelyakin at googlemail dot com 2024-03-06 21:32 ` 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-107083-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).