public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "saifi.khan at nishan dot io" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/113121] New: <print> failed to load pendings for ‘std::__format::__do_vformat_to’ Date: Sat, 23 Dec 2023 09:22:53 +0000 [thread overview] Message-ID: <bug-113121-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113121 Bug ID: 113121 Summary: <print> failed to load pendings for ‘std::__format::__do_vformat_to’ Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: saifi.khan at nishan dot io Target Milestone: --- built and working with g++ (GCC) 14.0.0 20231222 (experimental). When I attempt to compile header unit of <print> with the following command g++ -std=c++23 -v -g3 -fmodules-ts -x c++-system-header print errors out /opt/gcc/include/c++/14.0.0/print: In constructor ‘std::basic_format_arg<_Context>::basic_format_arg() [with _Context = std::basic_format_context<std::__format::_Sink_iter<char>, char>]’: /opt/gcc/include/c++/14.0.0/print:55:56: error: recursive lazy load 55 | vprint_nonunicode(FILE* __stream, string_view __fmt, format_args __args) | ^~~~~~~~~~~ /opt/gcc/include/c++/14.0.0/print:55:56: fatal error: failed to load pendings for ‘std::__format::__do_vformat_to’ With an earlier build 20231217, I did not encounter any error while trying to compile the header unit, instead when i compile test code. Please see https://gcc.gnu.org/pipermail/gcc-help/2023-December/143109.html
next reply other threads:[~2023-12-23 9:22 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-23 9:22 saifi.khan at nishan dot io [this message] 2024-01-18 19:27 ` [Bug c++/113121] " mpolacek at gcc dot gnu.org 2024-03-06 20:33 ` 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-113121-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).