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: Sat, 09 Oct 2021 00:15:18 +0000 [thread overview] Message-ID: <bug-98725-4-HUvXadc2FH@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 #9 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>: https://gcc.gnu.org/g:4997c8b30ecfc82f9e6ce874cbd3840e227522eb commit r12-4264-g4997c8b30ecfc82f9e6ce874cbd3840e227522eb Author: Jonathan Wakely <jwakely@redhat.com> Date: Fri Oct 8 14:48:04 2021 +0100 libstdc++: Enable vstring for wchar_t unconditionally [PR98725] None of these vstring specializations depend on libc support for wchar_t, so can be enabled unconditionally now that char_traits<wchar_t> is always available. libstdc++-v3/ChangeLog: PR libstdc++/98725 * include/ext/rc_string_base.h [!_GLIBCXX_USE_WCHAR_T] (__rc_string_base<wchar_t>): Define member function. * include/ext/vstring.h [!_GLIBCXX_USE_WCHAR_T] (hash<__gnu_cxx::__wvstring>): Define specialization. * include/ext/vstring_fwd.h [!_GLIBCXX_USE_WCHAR_T] (__wvstring) (__wsso_string, __wrc_string): Declare typedefs.
next prev parent reply other threads:[~2021-10-09 0:15 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 [this message] 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
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-HUvXadc2FH@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).