public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "nickbegg at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/99426] [modules] failed to read compiled module cluster 1186: Bad file data Date: Sun, 07 Apr 2024 12:33:40 +0000 [thread overview] Message-ID: <bug-99426-4-n102vnVzfY@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99426-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99426 --- Comment #8 from Nick Begg <nickbegg at gmail dot com> --- I've been testing with the proposed patch, and I am still getting the same errors.. /home/nick/inst/gcc-trunk-debug/bin/g++ -g -std=gnu++23 -Wall -Wextra -freport-bug --param=ggc-min-expand=10000 -MD -MT CMakeFiles/moduleMin.dir/main.cpp.o -MF CMakeFiles/moduleMin.dir/main.cpp.o.d -fmodules-ts -fmodule-mapper=CMakeFiles/moduleMin.dir/main.cpp.o.modmap -MD -fdeps-format=p1689r5 -x c++ -o CMakeFiles/moduleMin.dir/main.cpp.o -c /home/nick/src/moduleMin/main.cpp In module imported at /home/nick/src/moduleMin/main.cpp:3:1: modA: error: failed to read compiled module cluster 3000: Bad file data modA: note: compiled module file is ‘CMakeFiles/moduleMin.dir/modA.gcm’ modA: error: failed to read compiled module cluster 3001: Bad file data In file included from /home/nick/src/moduleMin/main.cpp:1: /home/nick/inst/gcc-trunk-debug/include/c++/14.0.1/format:1899:35: fatal error: failed to load pendings for ‘std::__format::__formatter_int’ 1899 | return _M_f._M_parse<char>(__pc); | ~~~~~~~~~~~~~~~~~~~^~~~~~ compilation terminated. I'm not sure if this is the same bug, or if I've uncovered a similar but distinct bug... Various values of --param=ggc-min-expand don't seem to make a difference.
next prev parent reply other threads:[~2024-04-07 12:33 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-06 7:54 [Bug c++/99426] New: " alexander.lelyakin at googlemail dot com 2021-03-09 15:56 ` [Bug c++/99426] " alexander.lelyakin at googlemail dot com 2021-03-12 5:40 ` alexander.lelyakin at googlemail dot com 2021-03-24 19:38 ` alexander.lelyakin at googlemail dot com 2021-03-30 1:34 ` mpolacek at gcc dot gnu.org 2021-03-30 6:50 ` alexander.lelyakin at googlemail dot com 2022-09-08 4:39 ` markmigm at gmail dot com 2024-02-27 2:15 ` ppalka at gcc dot gnu.org 2024-02-29 18:04 ` ppalka at gcc dot gnu.org 2024-04-03 21:19 ` ppalka at gcc dot gnu.org 2024-04-07 12:33 ` nickbegg at gmail dot com [this message] 2024-04-07 14:56 ` ppalka at gcc dot gnu.org 2024-04-07 20:49 ` nickbegg at gmail dot com 2024-04-12 19:52 ` ppalka at gcc dot gnu.org 2024-04-12 19:53 ` 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-99426-4-n102vnVzfY@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).