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++/114519] [14 Regression] GCC 14 trunk fails to compile chrono with -fno-char8_t -std=gnu++20 Date: Mon, 08 Apr 2024 16:45:24 +0000 [thread overview] Message-ID: <bug-114519-4-AsGl6E8gIb@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114519-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114519 --- Comment #5 from GCC 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:feb6a2d3569095706170c9400e93add27a66e034 commit r14-9839-gfeb6a2d3569095706170c9400e93add27a66e034 Author: Jonathan Wakely <jwakely@redhat.com> Date: Tue Apr 2 22:46:55 2024 +0100 libstdc++: Use char for _Utf8_view if char8_t isn't available [PR114519] Instead of just omitting the definition of __unicode::_Utf8_view when char8_t is disabled, we can make it use char instead. libstdc++-v3/ChangeLog: PR libstdc++/114519 * include/bits/unicode.h (_Utf8_view) [!__cpp_char8_t]: Define using char instead of char8_t. * testsuite/ext/unicode/view.cc: Use u8""sv literals to create string views, instead of std::u8string_view.
prev parent reply other threads:[~2024-04-08 16:45 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-28 15:20 [Bug c++/114519] New: " janisozaur+gcc at gmail dot com 2024-03-28 15:26 ` [Bug libstdc++/114519] " pinskia at gcc dot gnu.org 2024-03-28 21:31 ` redi at gcc dot gnu.org 2024-04-02 20:12 ` cvs-commit at gcc dot gnu.org 2024-04-02 20:13 ` [Bug libstdc++/114519] [14 Regression] " redi at gcc dot gnu.org 2024-04-08 16:45 ` 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-114519-4-AsGl6E8gIb@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).