public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/98725] Review what is disabled in libstdc++ by --disable-wchar_t Date: Wed, 24 Nov 2021 11:51:50 +0000 [thread overview] Message-ID: <bug-98725-4-xksZMpsd8B@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98725-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98725 --- Comment #15 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-11 branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>: https://gcc.gnu.org/g:ecc43c92151141e3e862a344f753516dc6d5d967 commit r11-9295-gecc43c92151141e3e862a344f753516dc6d5d967 Author: Jonathan Wakely <jwakely@redhat.com> Date: Fri Oct 8 14:26:09 2021 +0100 libstdc++: Define deleted wchar_t overloads unconditionally [PR 98725] We don't need to have <wchar.h> support in order to delete overloads for inserting wide characters into narrow streams. libstdc++-v3/ChangeLog: PR libstdc++/98725 * include/std/ostream (operator<<(basic_ostream<char, Tr>&, wchar_t)) (operator<<(basic_ostream<char, Tr>&, const wchar_t*)): Always define as deleted. Do not check _GLIBCXX_USE_WCHAR_T. (cherry picked from commit 9a89281c4005a51eeed058ca66bcce8df1dd1b24)
prev parent reply other threads:[~2021-11-24 11:51 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-18 11:08 [Bug libstdc++/98725] New: " redi at gcc dot gnu.org 2021-01-18 14:23 ` [Bug libstdc++/98725] " cvs-commit at gcc dot gnu.org 2021-01-18 14:24 ` redi at gcc dot gnu.org 2021-04-19 10:40 ` redi at gcc dot gnu.org 2021-10-08 12:03 ` redi at gcc dot gnu.org 2021-10-08 14:08 ` redi at gcc dot gnu.org 2021-10-08 14:48 ` redi at gcc dot gnu.org 2021-10-08 14:51 ` cvs-commit at gcc dot gnu.org 2021-10-08 19:12 ` redi at gcc dot gnu.org 2021-10-08 23:31 ` redi at gcc dot gnu.org 2021-10-09 0:15 ` cvs-commit at gcc dot gnu.org 2021-10-09 0:15 ` cvs-commit at gcc dot gnu.org 2021-10-09 0:15 ` cvs-commit at gcc dot gnu.org 2021-10-09 0:15 ` cvs-commit at gcc dot gnu.org 2021-10-09 0:15 ` cvs-commit at gcc dot gnu.org 2021-10-09 0:15 ` cvs-commit at gcc dot gnu.org 2021-10-09 0:16 ` redi at gcc dot gnu.org 2021-11-24 11:51 ` cvs-commit at gcc dot gnu.org [this message]
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-98725-4-xksZMpsd8B@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).