public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "alexander.lelyakin at googlemail 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: Fri, 12 Mar 2021 05:40:40 +0000 [thread overview] Message-ID: <bug-99426-4-zVmoL6eorC@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 #2 from Alexander Lelyakin <alexander.lelyakin at googlemail dot com> --- There is a shorter sequence: g++ -std=c++20 -fmodules-ts -x c++-system-header typeindex g++ -std=c++20 -fmodules-ts -x c++-system-header stop_token g++ -std=c++20 -fmodules-ts -x c++-system-header optional g++ -std=c++20 -fmodules-ts -x c++-system-header system_error g++ -std=c++20 -fmodules-ts -x c++-system-header streambuf g++ -std=c++20 -fmodules-ts -x c++-system-header exception g++ -std=c++20 -fmodules-ts -x c++-system-header unordered_map g++ -std=c++20 -fmodules-ts -x c++-system-header complex ---- In module imported at /usr/local/include/c++/11.0.1/ios:43:1, included from /usr/local/include/c++/11.0.1/istream:38, from /usr/local/include/c++/11.0.1/sstream:38, from /usr/local/include/c++/11.0.1/complex:45: /usr/local/include/c++/11.0.1/streambuf: error: failed to read compiled module cluster 1269: Bad file data /usr/local/include/c++/11.0.1/streambuf: note: compiled module file is ‘gcm.cache/./usr/local/include/c++/11.0.1/streambuf.gcm’ In file included from /usr/local/include/c++/11.0.1/string:55, from /usr/local/include/c++/11.0.1/bits/locale_classes.h:40, from /usr/local/include/c++/11.0.1/bits/ios_base.h:41, from /usr/local/include/c++/11.0.1/ios:42, from /usr/local/include/c++/11.0.1/istream:38, from /usr/local/include/c++/11.0.1/sstream:38, from /usr/local/include/c++/11.0.1/complex:45: /usr/local/include/c++/11.0.1/bits/basic_string.h:6608:54: fatal error: failed to load pendings for ‘__gnu_cxx::__stoa’ 6608 | __idx, __base); } | ^ compilation terminated. ---- g++ (GCC) 11.0.1 20210311 (experimental) Copyright (C) 2021 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
next prev parent reply other threads:[~2021-03-12 5:40 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 [this message] 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 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-zVmoL6eorC@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).