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] GCC 14 trunk fails to compile chrono with -fno-char8_t -std=gnu++20
Date: Tue, 02 Apr 2024 20:12:50 +0000	[thread overview]
Message-ID: <bug-114519-4-qT2tU8Ydxj@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 #3 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:21aa57e73b820395b7b01843d61ef5b84cd20d02

commit r14-9761-g21aa57e73b820395b7b01843d61ef5b84cd20d02
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Thu Mar 28 21:29:17 2024 +0000

    libstdc++: Guard uses of char8_t with __cpp_char8_t [PR114519]

    libstdc++-v3/ChangeLog:

            PR libstdc++/114519
            * include/bits/unicode.h (_Utf8_view): Guard with check for
            char8_t being enabled.
            (__literal_encoding_is_unicode): Guard use of char8_t with check
            for it being enabled.
            * testsuite/std/format/functions/114519.cc: New test.

  parent reply	other threads:[~2024-04-02 20:12 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 [this message]
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

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-qT2tU8Ydxj@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: link
Be 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).