public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "unlvsur at live dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/106953] New: C++23 add new headers for freestanding Date: Fri, 16 Sep 2022 08:39:47 +0000 [thread overview] Message-ID: <bug-106953-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106953 Bug ID: 106953 Summary: C++23 add new headers for freestanding Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: unlvsur at live dot com Target Milestone: --- https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2022/p1642r11.html It now requires utility, tuple, ratio to be fully freestanding. memory, functional, iterator and ranges to be partial freestanding. https://en.cppreference.com/w/cpp/freestanding Time to add them.
next reply other threads:[~2022-09-16 8:39 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-16 8:39 unlvsur at live dot com [this message] 2022-09-16 8:53 ` [Bug libstdc++/106953] " redi at gcc dot gnu.org 2022-09-16 22:33 ` cvs-commit at gcc dot gnu.org 2022-09-17 3:28 ` unlvsur at live dot com 2022-09-17 3:29 ` unlvsur at live dot com 2022-09-20 9:54 ` redi at gcc dot gnu.org 2022-10-03 14:45 ` cvs-commit at gcc dot gnu.org 2022-10-03 14:51 ` redi 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-106953-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).