public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "markmigm 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: Thu, 08 Sep 2022 04:39:49 +0000	[thread overview]
Message-ID: <bug-99426-4-nLN49YmdZf@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

Mark Millard <markmigm at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |markmigm at gmail dot com

--- Comment #5 from Mark Millard <markmigm at gmail dot com> ---
I've run into this sort of problem under Fedora 36 with its g++ 12.2.1 :

# rm -fr gcm.cache/*
# c++ -std=c++20 -pedantic -Wall -Wextra -fmodules-ts -g -fPIC ios
# c++ -std=c++20 -pedantic -Wall -Wextra -fmodules-ts -g -fPIC iostream
# c++ -std=c++20 -pedantic -Wall -Wextra -fmodules-ts -g -fPIC ostream
# c++ -std=c++20 -pedantic -Wall -Wextra -fmodules-ts -g -fPIC iomanip
In module imported at /usr/include/c++/12/istream:38:1,
        included from /usr/include/c++/12/sstream:38,
                 from /usr/include/c++/12/bits/quoted_string.h:38,
                 from /usr/include/c++/12/iomanip:45:
/usr/include/c++/12/ios: error: failed to read compiled module cluster 927: Bad
file data
/usr/include/c++/12/ios: note: compiled module file is
‘gcm.cache/./usr/include/c++/12/ios.gcm’
In file included from /usr/include/c++/12/string:53,
                 from /usr/include/c++/12/bits/locale_classes.h:40,
                 from /usr/include/c++/12/bits/ios_base.h:41,
                 from /usr/include/c++/12/iomanip:40:
/usr/include/c++/12/bits/basic_string.h:3972:40: fatal error: failed to load
pendings for ‘__gnu_cxx::__stoa’
 3972 |   { return __gnu_cxx::__stoa<long, int>(&std::strtol, "stoi",
__str.c_str(),
      |           
~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 3973 |                                         __idx, __base); }
      |                                         ~~~~~~~~~~~~~~
compilation terminated.

But moving ios to be the last of the 4 did not generate any messages:

# rm -fr gcm.cache/*
# c++ -std=c++20 -pedantic -Wall -Wextra -fmodules-ts -g -fPIC iostream
# c++ -std=c++20 -pedantic -Wall -Wextra -fmodules-ts -g -fPIC ostream
# c++ -std=c++20 -pedantic -Wall -Wextra -fmodules-ts -g -fPIC iomanip
# c++ -std=c++20 -pedantic -Wall -Wextra -fmodules-ts -g -fPIC ios

I've run into other examples of order dependencies. I've not found a
way to predict a order that will be tolerated.

The "Last reconfirmed" could be updated.

  parent reply	other threads:[~2022-09-08  4:39 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 [this message]
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-nLN49YmdZf@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: link
Be 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).