public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mends-sputter.0z at icloud dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/111785] New: [modules] ICE when compiling fmt lib as module Date: Thu, 12 Oct 2023 13:15:26 +0000 [thread overview] Message-ID: <bug-111785-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111785 Bug ID: 111785 Summary: [modules] ICE when compiling fmt lib as module Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: mends-sputter.0z at icloud dot com Target Milestone: --- Created attachment 56095 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56095&action=edit preprocessed output generated by -freport-bug GCC 14.0 from recent snapshot (20231008) on aarch64 Using built-in specs. COLLECT_GCC=g++ COLLECT_LTO_WRAPPER=/opt/gcc14/libexec/gcc/aarch64-unknown-linux-gnu/14.0.0/lto-wrapper Target: aarch64-unknown-linux-gnu Configured with: ../configure --prefix=/opt/gcc14 --enable-languages=c,c++ --disable-multilib Thread model: posix Supported LTO compression algorithms: zlib gcc version 14.0.0 20231008 (experimental) (GCC) When attempting to build fmt from https://github.com/fmtlib/fmt, with the following command: g++ -std=c++20 -fmodules-ts -I../include fmt.cc The compiler ICEs with the following error: fmt.cc:73:8: internal compiler error: in core_vals, at cp/module.cc:6262 73 | export module fmt; | ^ 0x9a9b67 trees_out::core_vals(tree_node*) ../../gcc/cp/module.cc:6262 0x9add5f trees_out::tree_node_vals(tree_node*) ../../gcc/cp/module.cc:7218 0x9add5f trees_out::tree_value(tree_node*) ../../gcc/cp/module.cc:9083 0x9a7c73 trees_out::tree_node(tree_node*) ../../gcc/cp/module.cc:9281 0x9a9537 trees_out::core_vals(tree_node*) ../../gcc/cp/module.cc:6171 0x9a5fb3 trees_out::tree_node_vals(tree_node*) ../../gcc/cp/module.cc:7218 0x9a5fb3 trees_out::decl_value(tree_node*, depset*) ../../gcc/cp/module.cc:7797 0x9b0823 depset::hash::find_dependencies(module_state*) ../../gcc/cp/module.cc:13328 0x9b16c7 module_state::write_begin(elf_out*, cpp_reader*, module_state_config&, unsigned int&) ../../gcc/cp/module.cc:17895 0x9b2a0f finish_module_processing(cpp_reader*) ../../gcc/cp/module.cc:20241 0x91df57 c_parse_final_cleanups() ../../gcc/cp/decl2.cc:5255 0xbe773f c_common_parse_file() ../../gcc/c-family/c-opts.cc:1296 attaching the file generated by -freport-bug - compressed with the gzip tool. Note that this is similar and involves the same file as reported in this other in a comment in a separate report: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108080#c7 however with gcc 14.0 snapshots, this fails with every level of optimization flags, although in each case the crash dump is slightly different and fails on a separate line.
next reply other threads:[~2023-10-12 13:15 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-12 13:15 mends-sputter.0z at icloud dot com [this message] 2023-10-16 19:11 ` [Bug c++/111785] " ppalka at gcc dot gnu.org 2023-10-17 17:00 ` mends-sputter.0z at icloud dot com 2023-10-17 17:09 ` mends-sputter.0z at icloud dot com 2023-10-17 18:44 ` ppalka at gcc dot gnu.org 2023-10-24 0:48 ` ppalka at gcc dot gnu.org 2024-03-06 21:35 ` 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-111785-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).