public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/108080] New: ICE: in core_vals, at cp/module.cc:6262 with -fmodule-header Date: Tue, 13 Dec 2022 06:51:05 +0000 [thread overview] Message-ID: <bug-108080-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108080 Bug ID: 108080 Summary: ICE: in core_vals, at cp/module.cc:6262 with -fmodule-header Product: gcc Version: 13.0 Status: UNCONFIRMED Keywords: ice-on-valid-code Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: zsojka at seznam dot cz Target Milestone: --- Host: x86_64-pc-linux-gnu Target: x86_64-pc-linux-gnu Created attachment 54077 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54077&action=edit reduced testcase Maybe related to PR107083 Compiler output: $ x86_64-pc-linux-gnu-g++ -fmodule-header testcase.C testcase.C: internal compiler error: in core_vals, at cp/module.cc:6262 0x7083ca trees_out::core_vals(tree_node*) /repo/gcc-trunk/gcc/cp/module.cc:6262 0xf3ea44 trees_out::tree_node_vals(tree_node*) /repo/gcc-trunk/gcc/cp/module.cc:7216 0xf3ea44 trees_out::tree_value(tree_node*) /repo/gcc-trunk/gcc/cp/module.cc:9081 0xf3a8b1 trees_out::tree_node(tree_node*) /repo/gcc-trunk/gcc/cp/module.cc:9279 0xf3bba0 trees_out::core_vals(tree_node*) /repo/gcc-trunk/gcc/cp/module.cc:6170 0xf3939a trees_out::tree_node_vals(tree_node*) /repo/gcc-trunk/gcc/cp/module.cc:7216 0xf3939a trees_out::decl_value(tree_node*, depset*) /repo/gcc-trunk/gcc/cp/module.cc:7795 0xf409e2 depset::hash::find_dependencies(module_state*) /repo/gcc-trunk/gcc/cp/module.cc:13326 0xf41171 module_state::write_begin(elf_out*, cpp_reader*, module_state_config&, unsigned int&) /repo/gcc-trunk/gcc/cp/module.cc:17893 0xf42574 finish_module_processing(cpp_reader*) /repo/gcc-trunk/gcc/cp/module.cc:20235 0xed1912 c_parse_final_cleanups() /repo/gcc-trunk/gcc/cp/decl2.cc:5148 0x10fd190 c_common_parse_file() /repo/gcc-trunk/gcc/c-family/c-opts.cc:1266 Please submit a full bug report, with preprocessed source (by using -freport-bug). Please include the complete backtrace with any bug report. See <https://gcc.gnu.org/bugs/> for instructions. $ x86_64-pc-linux-gnu-g++ -v Using built-in specs. COLLECT_GCC=/repo/gcc-trunk/binary-latest/bin/x86_64-pc-linux-gnu-g++ COLLECT_LTO_WRAPPER=/repo/gcc-trunk/binary-trunk-r13-4610-20221212132425-g14d0f82cab3-checking-yes-rtl-df-extra-amd64/bin/../libexec/gcc/x86_64-pc-linux-gnu/13.0.0/lto-wrapper Target: x86_64-pc-linux-gnu Configured with: /repo/gcc-trunk//configure --enable-languages=c,c++ --enable-valgrind-annotations --disable-nls --enable-checking=yes,rtl,df,extra --with-cloog --with-ppl --with-isl --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --target=x86_64-pc-linux-gnu --with-ld=/usr/bin/x86_64-pc-linux-gnu-ld --with-as=/usr/bin/x86_64-pc-linux-gnu-as --disable-libstdcxx-pch --prefix=/repo/gcc-trunk//binary-trunk-r13-4610-20221212132425-g14d0f82cab3-checking-yes-rtl-df-extra-amd64 Thread model: posix Supported LTO compression algorithms: zlib zstd gcc version 13.0.0 20221212 (experimental) (GCC)
next reply other threads:[~2022-12-13 6:51 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-13 6:51 zsojka at seznam dot cz [this message] 2022-12-13 6:53 ` [Bug c++/108080] " pinskia at gcc dot gnu.org 2022-12-13 6:53 ` pinskia at gcc dot gnu.org 2023-07-26 13:37 ` doko at gcc dot gnu.org 2023-07-26 13:39 ` doko at gcc dot gnu.org 2023-08-14 11:15 ` yagreg7 at gmail dot com 2023-08-14 11:21 ` yagreg7 at gmail dot com 2023-08-14 11:58 ` yagreg7 at gmail dot com 2024-03-06 21:32 ` ppalka at gcc dot gnu.org 2024-03-06 21:33 ` 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-108080-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).